Transaction Details
Tx hash
fdf990ab37cce293501461dc2e38eeca81749e1c6befad7a8b6ae0a11831d13e
Tx prefix hash
16866a8ae776270566ddba89c9ec6c6e55c62abf1ca0f7fdb50cec84b9a6e87a
Tx public key
4acd790d562d5df46dcef3bd0d2d6b5a7a77d6f7b9ad86b5edfbcb29ccdfc8d6
Age [y:d:h:m:s]
05:130:11:08:48
Timestamp [UCT] (epoch)
2019-07-25 13:09:40 (1564060180)
Block
227833 (1374474 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
014acd790d562d5df46dcef3bd0d2d6b5a7a77d6f7b9ad86b5edfbcb29ccdfc8d6021100000080f20f8dbf000000000000000000032100b4c3675e7c3eee696b645e1e6e19808e45ee4cbe2bdba20d9ee53b9579adece7
Outputs
1 output(s) for total of 18.179409598 ARQ
stealth address amount amount idx
00: bfab544744a3e1f0c0d23db27d0b8bb08f4739a2408643e9f0cc135413728270 18.179409598 1066442 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": 227851, 
  "vin": [ {
      "gen": {
        "height": 227833
      }
    }
  ], 
  "vout": [ {
      "amount": 18179409598, 
      "target": {
        "key": "bfab544744a3e1f0c0d23db27d0b8bb08f4739a2408643e9f0cc135413728270"
      }
    }
  ], 
  "extra": [ 1, 74, 205, 121, 13, 86, 45, 93, 244, 109, 206, 243, 189, 13, 45, 107, 90, 122, 119, 214, 247, 185, 173, 134, 181, 237, 251, 203, 41, 204, 223, 200, 214, 2, 17, 0, 0, 0, 128, 242, 15, 141, 191, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 180, 195, 103, 94, 124, 62, 238, 105, 107, 100, 94, 30, 110, 25, 128, 142, 69, 238, 76, 190, 43, 219, 162, 13, 158, 229, 59, 149, 121, 173, 236, 231
  ], 
  "rct_signatures": {
    "type": 0
  }
}