Transaction Details
Tx hash
5a9d14449d916cf5c75dce95418b94e426f9b7cf2e263665a19f7df3d9fba8c5
Tx prefix hash
c7e5708ea892b30e471571a9c8d34c8c955a3774878228abcb09938b76b1f8e6
Tx public key
aaf0a82100b7677e9c90ee7c136a13b4acb3a1eb6a4d67703c9f2b8b2d5e3cad
Age [y:d:h:m:s]
05:138:12:41:28
Timestamp [UCT] (epoch)
2019-07-12 22:42:44 (1562971364)
Block
218716 (1380410 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01aaf0a82100b7677e9c90ee7c136a13b4acb3a1eb6a4d67703c9f2b8b2d5e3cad021100000003ee3c55ab0000000000000000000321003d7fb8b6805a5504ce9a095c83d294d9a5cc3844ee29e8dedbef1e1f2dde4055
Outputs
1 output(s) for total of 18.258569575 ARQ
stealth address amount amount idx
00: fa0d5570d34cbcb8f34e0498702c9f4082cce4a50d1c47bf5d8452d2ce72acfe 18.258569575 1017363 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": 218734, 
  "vin": [ {
      "gen": {
        "height": 218716
      }
    }
  ], 
  "vout": [ {
      "amount": 18258569575, 
      "target": {
        "key": "fa0d5570d34cbcb8f34e0498702c9f4082cce4a50d1c47bf5d8452d2ce72acfe"
      }
    }
  ], 
  "extra": [ 1, 170, 240, 168, 33, 0, 183, 103, 126, 156, 144, 238, 124, 19, 106, 19, 180, 172, 179, 161, 235, 106, 77, 103, 112, 60, 159, 43, 139, 45, 94, 60, 173, 2, 17, 0, 0, 0, 3, 238, 60, 85, 171, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 61, 127, 184, 182, 128, 90, 85, 4, 206, 154, 9, 92, 131, 210, 148, 217, 165, 204, 56, 68, 238, 41, 232, 222, 219, 239, 30, 31, 45, 222, 64, 85
  ], 
  "rct_signatures": {
    "type": 0
  }
}