Transaction Details
Tx hash
83504832e1eab96292e5e64764e1f7add3e0d1d23493ada41ff0d7c13a9ebf26
Tx prefix hash
3574c864c9771a7f6fc000b71281b7caf5565ccc3ed0d1c40b64a40cce331f32
Tx public key
24bef3fcdf0f03a5e7e192927c531d25b0a3dd563a0c63b1db3e9dab6efd19d5
Age [y:d:h:m:s]
05:114:03:36:05
Timestamp [UCT] (epoch)
2019-07-30 10:15:22 (1564481722)
Block
231310 (1362916 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0124bef3fcdf0f03a5e7e192927c531d25b0a3dd563a0c63b1db3e9dab6efd19d5032100d6da219b58a16ae62499182df25d3d81dd35d39578bf888cb7d41959e90721e0021b00000000000000000000000000cf7975fa00000000000000000000
Outputs
1 output(s) for total of 18.149250171 ARQ
stealth address amount amount idx
00: 5db973ab30e3b492cd8c12d8afb1a64620585f07891e5b22cca4f7c5ed8a71f2 18.149250171 1076258 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": 231328, 
  "vin": [ {
      "gen": {
        "height": 231310
      }
    }
  ], 
  "vout": [ {
      "amount": 18149250171, 
      "target": {
        "key": "5db973ab30e3b492cd8c12d8afb1a64620585f07891e5b22cca4f7c5ed8a71f2"
      }
    }
  ], 
  "extra": [ 1, 36, 190, 243, 252, 223, 15, 3, 165, 231, 225, 146, 146, 124, 83, 29, 37, 176, 163, 221, 86, 58, 12, 99, 177, 219, 62, 157, 171, 110, 253, 25, 213, 3, 33, 0, 214, 218, 33, 155, 88, 161, 106, 230, 36, 153, 24, 45, 242, 93, 61, 129, 221, 53, 211, 149, 120, 191, 136, 140, 183, 212, 25, 89, 233, 7, 33, 224, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 207, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}