Transaction Details
Tx hash
15a4b80d58347de6f7c6022c8a6ac59ce67f2ac9700d96b24c2357c7d5f212aa
Tx prefix hash
de6e4e80307fea5ae7132843aa9a57c54dd6110735f9e740e03e2a6d78493403
Tx public key
d7ceb2f160e9184c602421e6bdd0ca392c9e274c0d0c07ff00f0c695aa33f3c1
Age [y:d:h:m:s]
05:137:10:38:05
Timestamp [UCT] (epoch)
2019-07-12 22:44:57 (1562971497)
Block
218717 (1379648 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01d7ceb2f160e9184c602421e6bdd0ca392c9e274c0d0c07ff00f0c695aa33f3c1021100000117091d2b5c000000000000000000032100f6b2680da64efcbaf7a0a2ef204b90342065adc08b32c0befa6e4d623efe28ee
Outputs
1 output(s) for total of 18.258560869 ARQ
stealth address amount amount idx
00: 8b38e42b1e74025242125531005cce01f1f5657d2e5a0c7a8abfb73d3e2af89f 18.258560869 1017364 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": 218735, 
  "vin": [ {
      "gen": {
        "height": 218717
      }
    }
  ], 
  "vout": [ {
      "amount": 18258560869, 
      "target": {
        "key": "8b38e42b1e74025242125531005cce01f1f5657d2e5a0c7a8abfb73d3e2af89f"
      }
    }
  ], 
  "extra": [ 1, 215, 206, 178, 241, 96, 233, 24, 76, 96, 36, 33, 230, 189, 208, 202, 57, 44, 158, 39, 76, 13, 12, 7, 255, 0, 240, 198, 149, 170, 51, 243, 193, 2, 17, 0, 0, 1, 23, 9, 29, 43, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 246, 178, 104, 13, 166, 78, 252, 186, 247, 160, 162, 239, 32, 75, 144, 52, 32, 101, 173, 192, 139, 50, 192, 190, 250, 110, 77, 98, 62, 254, 40, 238
  ], 
  "rct_signatures": {
    "type": 0
  }
}