Transaction Details
Tx hash
33269a0a2d90154a1d053842a62cd996d74cd7412eaf20170f795f5ed4c39d51
Tx prefix hash
30698ab6a748668c9e0fd3d29908f5ed95c33d73a9009b02257a273de0f49d28
Tx public key
b64bf6347be1853bf895f0957ecd518bb70b62bc02a2bc53bf84a2f42dda2dba
Age [y:d:h:m:s]
05:278:15:52:54
Timestamp [UCT] (epoch)
2018-12-27 20:19:34 (1545941974)
Block
78099 (1480865 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01b64bf6347be1853bf895f0957ecd518bb70b62bc02a2bc53bf84a2f42dda2dba03210046710b2fbeed94c3241841646713573a91282bf4bf83cfc9609a8123e8f1e81e021b000000000000000000000000005d53b68f00000000000000000000
Outputs
1 output(s) for total of 19.524808971 ARQ
stealth address amount amount idx
00: c81e3530e15d7700735b130c9d8d2590dcb4e819309ddf07a60dc43a3f780cc2 19.524808971 389057 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": 78117, 
  "vin": [ {
      "gen": {
        "height": 78099
      }
    }
  ], 
  "vout": [ {
      "amount": 19524808971, 
      "target": {
        "key": "c81e3530e15d7700735b130c9d8d2590dcb4e819309ddf07a60dc43a3f780cc2"
      }
    }
  ], 
  "extra": [ 1, 182, 75, 246, 52, 123, 225, 133, 59, 248, 149, 240, 149, 126, 205, 81, 139, 183, 11, 98, 188, 2, 162, 188, 83, 191, 132, 162, 244, 45, 218, 45, 186, 3, 33, 0, 70, 113, 11, 47, 190, 237, 148, 195, 36, 24, 65, 100, 103, 19, 87, 58, 145, 40, 43, 244, 191, 131, 207, 201, 96, 154, 129, 35, 232, 241, 232, 30, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 93, 83, 182, 143, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}