Transaction Details
Tx hash
6fa0cbe314764a74b16587d1a75886608fd4dd2c2c5455aa13bd2202ab8e9111
Tx prefix hash
da423ff014ce7019a3449382f20a847021762b3169f4987faafa5c92bf9aa148
Tx public key
48a3304f0cce3d41cfa0c3e3e5e9cf98270c16508da735dc500b0ed1797d7841
Age [y:d:h:m:s]
05:339:16:11:26
Timestamp [UCT] (epoch)
2018-12-28 10:55:02 (1545994502)
Block
78523 (1523863 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0148a3304f0cce3d41cfa0c3e3e5e9cf98270c16508da735dc500b0ed1797d7841032100c0c812499bde3df9a483439acb84d08e81389ca564764bc01a6acbdb2f11b58c021b000000000000000000000000004108f6ef00000000000000000000
Outputs
1 output(s) for total of 19.520924343 ARQ
stealth address amount amount idx
00: 88519647d51d56cf2bf1171e0d8cd433c9d9d926a46be97ad382df1d8b7c6b84 19.520924343 390122 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": 78541, 
  "vin": [ {
      "gen": {
        "height": 78523
      }
    }
  ], 
  "vout": [ {
      "amount": 19520924343, 
      "target": {
        "key": "88519647d51d56cf2bf1171e0d8cd433c9d9d926a46be97ad382df1d8b7c6b84"
      }
    }
  ], 
  "extra": [ 1, 72, 163, 48, 79, 12, 206, 61, 65, 207, 160, 195, 227, 229, 233, 207, 152, 39, 12, 22, 80, 141, 167, 53, 220, 80, 11, 14, 209, 121, 125, 120, 65, 3, 33, 0, 192, 200, 18, 73, 155, 222, 61, 249, 164, 131, 67, 154, 203, 132, 208, 142, 129, 56, 156, 165, 100, 118, 75, 192, 26, 106, 203, 219, 47, 17, 181, 140, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 65, 8, 246, 239, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}