Transaction Details
Tx hash
871c72e6cd576275dc84c0a268e2bbd73df904d65885ce50492c8f5e6da4aa34
Tx prefix hash
ab6f6f2d58a2fd42fdb9498e773eef9fc6c7393dff4e163fee8221322cb1c782
Tx public key
2af660b38e0eb099b2b6a52f8a3da5beae463aecb3f1d4356cf10444f42e8e07
Age [y:d:h:m:s]
05:313:17:26:08
Timestamp [UCT] (epoch)
2019-01-21 03:16:19 (1548040579)
Block
95373 (1505430 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
012af660b38e0eb099b2b6a52f8a3da5beae463aecb3f1d4356cf10444f42e8e07032100ce2cd9a20db740a3b8f0b88da744682b503d1f6a6f226cd1d50fc1ad1410830e021b000000000000000000000000000be93d4b00000000000000000000
Outputs
1 output(s) for total of 19.364645853 ARQ
stealth address amount amount idx
00: e9a64646c6bafe468da01c8f5470781e16e0becfacecf0910d4d4dc28b37eaf5 19.364645853 471029 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": 95391, 
  "vin": [ {
      "gen": {
        "height": 95373
      }
    }
  ], 
  "vout": [ {
      "amount": 19364645853, 
      "target": {
        "key": "e9a64646c6bafe468da01c8f5470781e16e0becfacecf0910d4d4dc28b37eaf5"
      }
    }
  ], 
  "extra": [ 1, 42, 246, 96, 179, 142, 14, 176, 153, 178, 182, 165, 47, 138, 61, 165, 190, 174, 70, 58, 236, 179, 241, 212, 53, 108, 241, 4, 68, 244, 46, 142, 7, 3, 33, 0, 206, 44, 217, 162, 13, 183, 64, 163, 184, 240, 184, 141, 167, 68, 104, 43, 80, 61, 31, 106, 111, 34, 108, 209, 213, 15, 193, 173, 20, 16, 131, 14, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 233, 61, 75, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}