Transaction Details
Tx hash
472d2d492f318f2920c9e5b32e6399ff12c75b6ca6ce6c5c774971fd62ba4f0b
Tx prefix hash
3393f60eac2354f1b6598a62b73cd7619ac6cede4aa4c4f8e5f7c61e7595a8a4
Tx public key
a808349eaf60ee203bd90207ddd690a2a9b6d405fd0f18274f845f4e1d929cfa
Age [y:d:h:m:s]
05:140:20:20:26
Timestamp [UCT] (epoch)
2019-07-11 17:43:29 (1562867009)
Block
217872 (1382035 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01a808349eaf60ee203bd90207ddd690a2a9b6d405fd0f18274f845f4e1d929cfa02110000004af20f8dbf000000000000000000032100d7a60e8a38d80dcf5f4ccbdbdf9764d9afd053f3d39e3be463500faf1507e65f
Outputs
1 output(s) for total of 18.265963087 ARQ
stealth address amount amount idx
00: 51b60e01d90c2b4ea40ac62ce9d685c2a68afae3d95390da327ff40fe69f444d 18.265963087 1012417 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": 217890, 
  "vin": [ {
      "gen": {
        "height": 217872
      }
    }
  ], 
  "vout": [ {
      "amount": 18265963087, 
      "target": {
        "key": "51b60e01d90c2b4ea40ac62ce9d685c2a68afae3d95390da327ff40fe69f444d"
      }
    }
  ], 
  "extra": [ 1, 168, 8, 52, 158, 175, 96, 238, 32, 59, 217, 2, 7, 221, 214, 144, 162, 169, 182, 212, 5, 253, 15, 24, 39, 79, 132, 95, 78, 29, 146, 156, 250, 2, 17, 0, 0, 0, 74, 242, 15, 141, 191, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 215, 166, 14, 138, 56, 216, 13, 207, 95, 76, 203, 219, 223, 151, 100, 217, 175, 208, 83, 243, 211, 158, 59, 228, 99, 80, 15, 175, 21, 7, 230, 95
  ], 
  "rct_signatures": {
    "type": 0
  }
}