Transaction Details
Tx hash
cf61c534f7dc69f8c96051aa3e03d65ef16be7ddc23fa8962a2ab4b9484d627a
Tx prefix hash
3ef93cec581824ab308311aa1f2c17882c11c3e9139618f388794149b1af8c19
Tx public key
c51109cc28a1944659b194f9439e5952be97e822a2127abce104b621f83be50c
Age [y:d:h:m:s]
05:170:21:45:40
Timestamp [UCT] (epoch)
2019-01-20 04:26:44 (1547958404)
Block
94673 (1404479 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c51109cc28a1944659b194f9439e5952be97e822a2127abce104b621f83be50c032100ced33e3cb51af8987278e55e5bb3781d84b320700b5201b78a7577e9ca922fa7021b00000000000000000000000000a6a3caf700000000000000000000
Outputs
1 output(s) for total of 19.371110582 ARQ
stealth address amount amount idx
00: a0d972c433f33d91376c2c22d59ad0fbc7340801dcb535836e4198d4378e294b 19.371110582 467614 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": 94691, 
  "vin": [ {
      "gen": {
        "height": 94673
      }
    }
  ], 
  "vout": [ {
      "amount": 19371110582, 
      "target": {
        "key": "a0d972c433f33d91376c2c22d59ad0fbc7340801dcb535836e4198d4378e294b"
      }
    }
  ], 
  "extra": [ 1, 197, 17, 9, 204, 40, 161, 148, 70, 89, 177, 148, 249, 67, 158, 89, 82, 190, 151, 232, 34, 162, 18, 122, 188, 225, 4, 182, 33, 248, 59, 229, 12, 3, 33, 0, 206, 211, 62, 60, 181, 26, 248, 152, 114, 120, 229, 94, 91, 179, 120, 29, 132, 179, 32, 112, 11, 82, 1, 183, 138, 117, 119, 233, 202, 146, 47, 167, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 166, 163, 202, 247, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}