Transaction Details
Tx hash
f32a1deb612e190cd8f1b97dd7190934d04fceb8f4b958e71b0a457cff5ec6fe
Tx prefix hash
b9e60aac2979b75b67899c3a8d63a5615b451ccd12445f3b4df961fe374becf2
Tx public key
b8d6e39933e3ea1072c19199e4de4984a37f741f0a8648aa4ebfc5e8e5c05b7b
Age [y:d:h:m:s]
05:175:01:52:48
Timestamp [UCT] (epoch)
2019-04-16 07:29:39 (1555399779)
Block
156001 (1407080 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01b8d6e39933e3ea1072c19199e4de4984a37f741f0a8648aa4ebfc5e8e5c05b7b032100bc9f0e5a4cf6fb3b1b1971dea64848b4c01fd34b04f55ddd8848414d3fb87d3d0210000000022e2201000000000000000000
Outputs
1 output(s) for total of 18.812835666 ARQ
stealth address amount amount idx
00: da24655d7f95499888ed2b4774ad60b7513cabb4fd694cff957b848d70b3bcee 18.812835666 714747 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": 156019, 
  "vin": [ {
      "gen": {
        "height": 156001
      }
    }
  ], 
  "vout": [ {
      "amount": 18812835666, 
      "target": {
        "key": "da24655d7f95499888ed2b4774ad60b7513cabb4fd694cff957b848d70b3bcee"
      }
    }
  ], 
  "extra": [ 1, 184, 214, 227, 153, 51, 227, 234, 16, 114, 193, 145, 153, 228, 222, 73, 132, 163, 127, 116, 31, 10, 134, 72, 170, 78, 191, 197, 232, 229, 192, 91, 123, 3, 33, 0, 188, 159, 14, 90, 76, 246, 251, 59, 27, 25, 113, 222, 166, 72, 72, 180, 192, 31, 211, 75, 4, 245, 93, 221, 136, 72, 65, 77, 63, 184, 125, 61, 2, 16, 0, 0, 0, 2, 46, 34, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}