Transaction Details
Tx hash
5b1ebf1e9d21b17f6ed9b41394010efd3213a3df9999db6663bf04675d594fab
Tx prefix hash
542225d2921c9179a4dd88336f1cfda6cb1e0c6f9a3df32c4fa02cdc30e56bd4
Tx public key
a5a07c2556a7afdd5da2a4afe5b90cf3b77ddb5174ef1fd1aee1abb0a447a14e
Age [y:d:h:m:s]
05:103:18:30:14
Timestamp [UCT] (epoch)
2019-08-15 03:15:13 (1565838913)
Block
242596 (1355405 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a5a07c2556a7afdd5da2a4afe5b90cf3b77ddb5174ef1fd1aee1abb0a447a14e0321003e414877f574fa326b87a0f55481356b0d000e1094990f6777a17e6ec4f2c02b021b00000000000000000000000003a91522be00000000000000000000
Outputs
1 output(s) for total of 18.051840774 ARQ
stealth address amount amount idx
00: b3a33efb5f0d4838d5b27349712efa8c016053843afc0cf602b15d3c3e0df623 18.051840774 1100712 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": 242614, 
  "vin": [ {
      "gen": {
        "height": 242596
      }
    }
  ], 
  "vout": [ {
      "amount": 18051840774, 
      "target": {
        "key": "b3a33efb5f0d4838d5b27349712efa8c016053843afc0cf602b15d3c3e0df623"
      }
    }
  ], 
  "extra": [ 1, 165, 160, 124, 37, 86, 167, 175, 221, 93, 162, 164, 175, 229, 185, 12, 243, 183, 125, 219, 81, 116, 239, 31, 209, 174, 225, 171, 176, 164, 71, 161, 78, 3, 33, 0, 62, 65, 72, 119, 245, 116, 250, 50, 107, 135, 160, 245, 84, 129, 53, 107, 13, 0, 14, 16, 148, 153, 15, 103, 119, 161, 126, 110, 196, 242, 192, 43, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 169, 21, 34, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}