Transaction Details
Tx hash
a8721e3bb2a8adcec90b07c2e59095df0337a8d6b7dcf6bcda8c3b4985c84411
Tx prefix hash
47f41292f61f8b9ad46e53b9411a44b206a136aea89b44642f96fdcdf09971c6
Tx public key
e248b41904e8e9554a8c5551445d6dae5db3d931ae0d36a0c66645e0fbf9aed1
Age [y:d:h:m:s]
05:117:06:45:00
Timestamp [UCT] (epoch)
2019-08-01 04:09:27 (1564632567)
Block
232580 (1365100 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e248b41904e8e9554a8c5551445d6dae5db3d931ae0d36a0c66645e0fbf9aed10321003f49e8d497c3b69e9060b41508e9c021cf0c83262172f076be42b0a28a83f4ff021b00000000000000000000000007560b689f00000000000000000000
Outputs
1 output(s) for total of 18.138262615 ARQ
stealth address amount amount idx
00: 422304966761a51cf2dc2444f6e099ca4a20b9cf4e5b65b91499b916dc854b4b 18.138262615 1080195 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": 232598, 
  "vin": [ {
      "gen": {
        "height": 232580
      }
    }
  ], 
  "vout": [ {
      "amount": 18138262615, 
      "target": {
        "key": "422304966761a51cf2dc2444f6e099ca4a20b9cf4e5b65b91499b916dc854b4b"
      }
    }
  ], 
  "extra": [ 1, 226, 72, 180, 25, 4, 232, 233, 85, 74, 140, 85, 81, 68, 93, 109, 174, 93, 179, 217, 49, 174, 13, 54, 160, 198, 102, 69, 224, 251, 249, 174, 209, 3, 33, 0, 63, 73, 232, 212, 151, 195, 182, 158, 144, 96, 180, 21, 8, 233, 192, 33, 207, 12, 131, 38, 33, 114, 240, 118, 190, 66, 176, 162, 138, 131, 244, 255, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 86, 11, 104, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}