Transaction Details
Tx hash
7428aeee695e5b6e3d19eabe1fbef64e76f85234c9528dae28c4e39da2dda566
Tx prefix hash
dde03cd8cd61d83c16eef1dc7ce9cb7789fa0b7cc43abe31df3894b32ff14d5d
Tx public key
be0f0e3f3babe9085fba8a12f25d10d4e44bfb894d1f9052819e0a8f5339c746
Age [y:d:h:m:s]
05:120:22:15:12
Timestamp [UCT] (epoch)
2019-08-01 23:00:16 (1564700416)
Block
233152 (1367668 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01be0f0e3f3babe9085fba8a12f25d10d4e44bfb894d1f9052819e0a8f5339c746032100d3d3b1332aea705fdc88e6f7655d26942c95c5e5a0a878db4206c37c9ae9e9f5021b00000000000000000000000007ea3771c800000000000000000000
Outputs
1 output(s) for total of 18.133316062 ARQ
stealth address amount amount idx
00: 75984cdfaed470dff415d0a7ce3d0b95d87dff6188b3798e1272fe91ca3e37b2 18.133316062 1081602 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": 233170, 
  "vin": [ {
      "gen": {
        "height": 233152
      }
    }
  ], 
  "vout": [ {
      "amount": 18133316062, 
      "target": {
        "key": "75984cdfaed470dff415d0a7ce3d0b95d87dff6188b3798e1272fe91ca3e37b2"
      }
    }
  ], 
  "extra": [ 1, 190, 15, 14, 63, 59, 171, 233, 8, 95, 186, 138, 18, 242, 93, 16, 212, 228, 75, 251, 137, 77, 31, 144, 82, 129, 158, 10, 143, 83, 57, 199, 70, 3, 33, 0, 211, 211, 177, 51, 42, 234, 112, 95, 220, 136, 230, 247, 101, 93, 38, 148, 44, 149, 197, 229, 160, 168, 120, 219, 66, 6, 195, 124, 154, 233, 233, 245, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 234, 55, 113, 200, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}