Transaction Details
Tx hash
b36fdd33ddfd5bd7a2044ca7f4b9c8032ae569cfeaba6831fcf15c708e76fa69
Tx prefix hash
45e1c4bce7abf1a3f501c62fbc8a02676663cd83f6fc5ce1eefdfb3a9698cd2b
Tx public key
e0fbf28a3f89c00a0b6ac6d8dbe5544e36644b1f75b7cd70a494bc9a60c0f5bf
Age [y:d:h:m:s]
05:110:22:15:34
Timestamp [UCT] (epoch)
2019-08-10 19:35:53 (1565465753)
Block
239497 (1360518 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e0fbf28a3f89c00a0b6ac6d8dbe5544e36644b1f75b7cd70a494bc9a60c0f5bf03210080fab9c11e02c38835c18e0ef9cf836a1d8dcc60547a601c71efaf39623b3c58021b000000000000000000000000056efd0e1700000000000000000000
Outputs
1 output(s) for total of 18.078536036 ARQ
stealth address amount amount idx
00: bcabe1ca797eefab0eeaa9c2425962bde007a66272d097b407d77a020b4fddc1 18.078536036 1095066 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": 239515, 
  "vin": [ {
      "gen": {
        "height": 239497
      }
    }
  ], 
  "vout": [ {
      "amount": 18078536036, 
      "target": {
        "key": "bcabe1ca797eefab0eeaa9c2425962bde007a66272d097b407d77a020b4fddc1"
      }
    }
  ], 
  "extra": [ 1, 224, 251, 242, 138, 63, 137, 192, 10, 11, 106, 198, 216, 219, 229, 84, 78, 54, 100, 75, 31, 117, 183, 205, 112, 164, 148, 188, 154, 96, 192, 245, 191, 3, 33, 0, 128, 250, 185, 193, 30, 2, 195, 136, 53, 193, 142, 14, 249, 207, 131, 106, 29, 141, 204, 96, 84, 122, 96, 28, 113, 239, 175, 57, 98, 59, 60, 88, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 110, 253, 14, 23, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}