Transaction Details
Tx hash
e51a0e9355a92f01e13fcc7d11b496be4b20f206c0dc75e8518be7dd75b27546
Tx prefix hash
470a1d7167e61896a2920bb2e8b61648bf3a89b5cffd70a9d1ed64042cdf9637
Tx public key
bd121c39cd155c69aabd6ff8d4c77906720eb8a3f124dc39481021d88f91164a
Age [y:d:h:m:s]
05:324:22:06:31
Timestamp [UCT] (epoch)
2019-01-09 20:00:52 (1547064052)
Block
87264 (1513481 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bd121c39cd155c69aabd6ff8d4c77906720eb8a3f124dc39481021d88f91164a0321005280e0262fa606b97d6dda8ecfc5f14f231592d782d6375926736ff3f8bbe2cb021b000000000000000000000000002dd5b34f00000000000000000000
Outputs
1 output(s) for total of 19.439667564 ARQ
stealth address amount amount idx
00: 20976146e1c94a2363b2db848e8f8d6b8c8c5a7c55fd053a074daba9e3facb69 19.439667564 431190 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": 87282, 
  "vin": [ {
      "gen": {
        "height": 87264
      }
    }
  ], 
  "vout": [ {
      "amount": 19439667564, 
      "target": {
        "key": "20976146e1c94a2363b2db848e8f8d6b8c8c5a7c55fd053a074daba9e3facb69"
      }
    }
  ], 
  "extra": [ 1, 189, 18, 28, 57, 205, 21, 92, 105, 170, 189, 111, 248, 212, 199, 121, 6, 114, 14, 184, 163, 241, 36, 220, 57, 72, 16, 33, 216, 143, 145, 22, 74, 3, 33, 0, 82, 128, 224, 38, 47, 166, 6, 185, 125, 109, 218, 142, 207, 197, 241, 79, 35, 21, 146, 215, 130, 214, 55, 89, 38, 115, 111, 243, 248, 187, 226, 203, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 45, 213, 179, 79, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}