Transaction Details
Tx hash
54e84c3a563fdbe90417726fe6f6c692b3bbd158e27eea7aeba8ddf8a271b837
Tx prefix hash
8057de00d1e3b5164f60cdfcaa2998a44e6bdf14216d8f3f52bd7dc7ad0f9e3d
Tx public key
bf63de72e10583a2d54bc32d8d9fdad254e07f60ecb8d73f883269b5ab83070c
Age [y:d:h:m:s]
05:154:00:12:17
Timestamp [UCT] (epoch)
2019-06-26 10:18:11 (1561544291)
Block
206859 (1391537 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bf63de72e10583a2d54bc32d8d9fdad254e07f60ecb8d73f883269b5ab83070c032100069a02fb7a058e3cb730c8f6977412d9eebc886aeaabbd56f40339c6d93f8a10021b0000000000000000000000000002eefee900000000000000000000
Outputs
1 output(s) for total of 18.362093341 ARQ
stealth address amount amount idx
00: fa05b5b6b1cfe0074c15c8d70912dacb0519d3e094eba75f9fcb9a829e0e0f3a 18.362093341 948189 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": 206877, 
  "vin": [ {
      "gen": {
        "height": 206859
      }
    }
  ], 
  "vout": [ {
      "amount": 18362093341, 
      "target": {
        "key": "fa05b5b6b1cfe0074c15c8d70912dacb0519d3e094eba75f9fcb9a829e0e0f3a"
      }
    }
  ], 
  "extra": [ 1, 191, 99, 222, 114, 225, 5, 131, 162, 213, 75, 195, 45, 141, 159, 218, 210, 84, 224, 127, 96, 236, 184, 215, 63, 136, 50, 105, 181, 171, 131, 7, 12, 3, 33, 0, 6, 154, 2, 251, 122, 5, 142, 60, 183, 48, 200, 246, 151, 116, 18, 217, 238, 188, 136, 106, 234, 171, 189, 86, 244, 3, 57, 198, 217, 63, 138, 16, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 238, 254, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}