Transaction Details
Tx hash
10d499d514e77dc8722dc623e7acce6611715bc4218e701a477066fde6c9aa64
Tx prefix hash
3653004e7bae1d09bdf969a75a09d7b070525db6934d7ef0955328b79cefb539
Tx public key
3e5788997e0555b1debc464777af954c2d0b6ff1c2dd09947bae8af6e43491f7
Age [y:d:h:m:s]
05:116:10:54:50
Timestamp [UCT] (epoch)
2019-08-05 10:26:38 (1565000798)
Block
235653 (1364466 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013e5788997e0555b1debc464777af954c2d0b6ff1c2dd09947bae8af6e43491f7032100e5ec29c424a8c4e555154d32bc1bcc0e5c47e8d969e176320a0d6ed1e133aefb021b000000000000000000000000020da5dd6800000000000000000000
Outputs
1 output(s) for total of 18.111703703 ARQ
stealth address amount amount idx
00: 27938250579f1ec1aa2752980fde6c6aa228dd4736da66e172f12d6e3699a867 18.111703703 1086964 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": 235671, 
  "vin": [ {
      "gen": {
        "height": 235653
      }
    }
  ], 
  "vout": [ {
      "amount": 18111703703, 
      "target": {
        "key": "27938250579f1ec1aa2752980fde6c6aa228dd4736da66e172f12d6e3699a867"
      }
    }
  ], 
  "extra": [ 1, 62, 87, 136, 153, 126, 5, 85, 177, 222, 188, 70, 71, 119, 175, 149, 76, 45, 11, 111, 241, 194, 221, 9, 148, 123, 174, 138, 246, 228, 52, 145, 247, 3, 33, 0, 229, 236, 41, 196, 36, 168, 196, 229, 85, 21, 77, 50, 188, 27, 204, 14, 92, 71, 232, 217, 105, 225, 118, 50, 10, 13, 110, 209, 225, 51, 174, 251, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 13, 165, 221, 104, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}