Transaction Details
Tx hash
f2dae74063bade7ef91187d87ed8ab1041e1dd44c087082f82d88f9c3eae6a9f
Tx prefix hash
8769ae806f3a529e3bede6a5e1416b64cf876c96ae23e983c9d612bd7a96bb4b
Tx public key
e1334880a582bfd953ac62391f86fd680aec3a3ae068c67928c7e6af140a8d6e
Age [y:d:h:m:s]
05:303:03:26:40
Timestamp [UCT] (epoch)
2019-01-28 17:18:48 (1548695928)
Block
100727 (1497975 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e1334880a582bfd953ac62391f86fd680aec3a3ae068c67928c7e6af140a8d6e032100153f3e8dd6a1bafa26f3bdd47c2776efb71666475f9300af0cc5a41b6f1a7f7b021b0000000000000000000000000010e59e0d00000000000000000000
Outputs
1 output(s) for total of 19.315271222 ARQ
stealth address amount amount idx
00: 9f24ec61903ebe775881da1d1c25efa3437688bdee1b715fb42a9b5728f15702 19.315271222 497778 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 100745, 
  "vin": [ {
      "gen": {
        "height": 100727
      }
    }
  ], 
  "vout": [ {
      "amount": 19315271222, 
      "target": {
        "key": "9f24ec61903ebe775881da1d1c25efa3437688bdee1b715fb42a9b5728f15702"
      }
    }
  ], 
  "extra": [ 1, 225, 51, 72, 128, 165, 130, 191, 217, 83, 172, 98, 57, 31, 134, 253, 104, 10, 236, 58, 58, 224, 104, 198, 121, 40, 199, 230, 175, 20, 10, 141, 110, 3, 33, 0, 21, 63, 62, 141, 214, 161, 186, 250, 38, 243, 189, 212, 124, 39, 118, 239, 183, 22, 102, 71, 95, 147, 0, 175, 12, 197, 164, 27, 111, 26, 127, 123, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 16, 229, 158, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}