Transaction Details
Tx hash
48b90aa53613e43a2958c32c648c07c2eee1954a980aec3eaa09d261fc0719a0
Tx prefix hash
2855f748485a7b7e76e655692bb0b6e0f1729c7c3209aebc5651c21d01d1324a
Tx public key
e4000ba3563c2c5a315f2c94c5e9d948f8ec206726b52ef73b1e9c2b57b832e7
Age [y:d:h:m:s]
05:310:23:51:46
Timestamp [UCT] (epoch)
2019-01-14 14:59:41 (1547477981)
Block
90707 (1503544 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e4000ba3563c2c5a315f2c94c5e9d948f8ec206726b52ef73b1e9c2b57b832e703210096d3c133044e6d815b934a31db0225a27d9ba3d46acd46ca489041f14ea4a205021b0000000000000000000000000026734c3b00000000000000000000
Outputs
1 output(s) for total of 19.408011759 ARQ
stealth address amount amount idx
00: 7ca658f9df9334e7b6c74d14084a4a8c03620a48a3fde7653fc4de74ea53e1bf 19.408011759 447913 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": 90725, 
  "vin": [ {
      "gen": {
        "height": 90707
      }
    }
  ], 
  "vout": [ {
      "amount": 19408011759, 
      "target": {
        "key": "7ca658f9df9334e7b6c74d14084a4a8c03620a48a3fde7653fc4de74ea53e1bf"
      }
    }
  ], 
  "extra": [ 1, 228, 0, 11, 163, 86, 60, 44, 90, 49, 95, 44, 148, 197, 233, 217, 72, 248, 236, 32, 103, 38, 181, 46, 247, 59, 30, 156, 43, 87, 184, 50, 231, 3, 33, 0, 150, 211, 193, 51, 4, 78, 109, 129, 91, 147, 74, 49, 219, 2, 37, 162, 125, 155, 163, 212, 106, 205, 70, 202, 72, 144, 65, 241, 78, 164, 162, 5, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 38, 115, 76, 59, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}