Transaction Details
Tx hash
74ae54f883b926b4319cf2d17e0847bf81b0648192847538b4b31adfe27f73a1
Tx prefix hash
a5a4a9e1ffeef61efee9c5e3970c710bccedbc8fe6d69372a069a77461b3c019
Tx public key
f5a4ef7c363f4eae52aeadcfdb3c56dc61b9ba1fff7a1b7ba0cae7d3f51faf42
Age [y:d:h:m:s]
05:140:17:29:42
Timestamp [UCT] (epoch)
2019-07-03 19:48:45 (1562183325)
Block
212167 (1382040 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f5a4ef7c363f4eae52aeadcfdb3c56dc61b9ba1fff7a1b7ba0cae7d3f51faf4203210033b828712e6d9b6d5a95adf8b3aab9f2108a282731c8d1b7232e63a1b7dd885b021b000000000000000000000000003bc4c81900000000000000000000
Outputs
1 output(s) for total of 18.315676690 ARQ
stealth address amount amount idx
00: fdba9ab084be43f78db9eb2af3b240a7101b949dbf5f7d9fde8d846d1b0fe18c 18.315676690 979681 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": 212185, 
  "vin": [ {
      "gen": {
        "height": 212167
      }
    }
  ], 
  "vout": [ {
      "amount": 18315676690, 
      "target": {
        "key": "fdba9ab084be43f78db9eb2af3b240a7101b949dbf5f7d9fde8d846d1b0fe18c"
      }
    }
  ], 
  "extra": [ 1, 245, 164, 239, 124, 54, 63, 78, 174, 82, 174, 173, 207, 219, 60, 86, 220, 97, 185, 186, 31, 255, 122, 27, 123, 160, 202, 231, 211, 245, 31, 175, 66, 3, 33, 0, 51, 184, 40, 113, 46, 109, 155, 109, 90, 149, 173, 248, 179, 170, 185, 242, 16, 138, 40, 39, 49, 200, 209, 183, 35, 46, 99, 161, 183, 221, 136, 91, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 59, 196, 200, 25, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}