Transaction Details
Tx hash
1e02465f3e421043205f853cde70c2a674689164e2cbc47768e985510443e7d0
Tx prefix hash
7b04adbf7a36baabd2a69244af1eaf7bee6ac4a265e6ed2bc803edb1db1fe85d
Tx public key
dd1b532a96287f3be96345f5f8dec0015b7df0eb2c0ef8113e0491a5f293e6c8
Age [y:d:h:m:s]
05:070:00:36:53
Timestamp [UCT] (epoch)
2019-09-17 03:02:34 (1568689354)
Block
265785 (1331689 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01dd1b532a96287f3be96345f5f8dec0015b7df0eb2c0ef8113e0491a5f293e6c8021100000822e779a7ea000000000000000000032100fbfe1a4c5e0c9b20e411313ac8c4e8b5aa7142482ed27f6c0e22771398e5f5b6
Outputs
1 output(s) for total of 20.264945464 ARQ
stealth address amount amount idx
00: c131e6314035facabcb3d4b8850f8b091e56c8b28b96797ec916260b58b4d314 20.264945464 1190080 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": 265803, 
  "vin": [ {
      "gen": {
        "height": 265785
      }
    }
  ], 
  "vout": [ {
      "amount": 20264945464, 
      "target": {
        "key": "c131e6314035facabcb3d4b8850f8b091e56c8b28b96797ec916260b58b4d314"
      }
    }
  ], 
  "extra": [ 1, 221, 27, 83, 42, 150, 40, 127, 59, 233, 99, 69, 245, 248, 222, 192, 1, 91, 125, 240, 235, 44, 14, 248, 17, 62, 4, 145, 165, 242, 147, 230, 200, 2, 17, 0, 0, 8, 34, 231, 121, 167, 234, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 251, 254, 26, 76, 94, 12, 155, 32, 228, 17, 49, 58, 200, 196, 232, 181, 170, 113, 66, 72, 46, 210, 127, 108, 14, 34, 119, 19, 152, 229, 245, 182
  ], 
  "rct_signatures": {
    "type": 0
  }
}