Transaction Details
Tx hash
0eeb6ec8213de5ae56200c9f9c5ec94429bffd3f21512ef4ddf547cba4bbb3a5
Tx prefix hash
3b1138498eb136d42d8b09408c213f6986d78738f6c6d02d0c24fc3ab77f3e57
Tx public key
0f5dc4a9a6706d32d6102b86acd6ad01bae6e1d2e2c9d413e972c2bf4efae76c
Age [y:d:h:m:s]
05:167:22:22:35
Timestamp [UCT] (epoch)
2019-06-12 20:22:52 (1560370972)
Block
197192 (1401444 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010f5dc4a9a6706d32d6102b86acd6ad01bae6e1d2e2c9d413e972c2bf4efae76c032100dd73c22a43f1a3bf003205a03bb2491cc9b63eba4718ebfea372e20f8b6ef53f021b00000000000000000000000000cd56ee0d00000000000000000000
Outputs
1 output(s) for total of 18.446930370 ARQ
stealth address amount amount idx
00: e5d67d2f4205f4ebb7c240e6995de76dad8915a7f578654c9078c080a7b719eb 18.446930370 891958 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": 197210, 
  "vin": [ {
      "gen": {
        "height": 197192
      }
    }
  ], 
  "vout": [ {
      "amount": 18446930370, 
      "target": {
        "key": "e5d67d2f4205f4ebb7c240e6995de76dad8915a7f578654c9078c080a7b719eb"
      }
    }
  ], 
  "extra": [ 1, 15, 93, 196, 169, 166, 112, 109, 50, 214, 16, 43, 134, 172, 214, 173, 1, 186, 230, 225, 210, 226, 201, 212, 19, 233, 114, 194, 191, 78, 250, 231, 108, 3, 33, 0, 221, 115, 194, 42, 67, 241, 163, 191, 0, 50, 5, 160, 59, 178, 73, 28, 201, 182, 62, 186, 71, 24, 235, 254, 163, 114, 226, 15, 139, 110, 245, 63, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 205, 86, 238, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}