Transaction Details
Tx hash
c956be6c2192ae66f3bde09a0a2baa90ad2df6a62ff7d4a6ce176bf9ee40e04f
Tx prefix hash
18b257c4bf914a8aa327738b1824e781d8b556372513dd6b94613341f1daddfc
Tx public key
6f28e0c8407d672d3a6de836e5fbb9e280ec8a0cf59f4476f079d2e6ebd9e60e
Age [y:d:h:m:s]
05:222:05:11:26
Timestamp [UCT] (epoch)
2019-04-22 15:07:01 (1555945621)
Block
160566 (1440228 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016f28e0c8407d672d3a6de836e5fbb9e280ec8a0cf59f4476f079d2e6ebd9e60e032100e4a38da695fde6b0366995e906ec14ae42ecbf98b3265a0e1d7d3dcd3ab8968c021b000000000000000000000000000411a68800000000000000000000
Outputs
1 output(s) for total of 18.771929136 ARQ
stealth address amount amount idx
00: e86d57d1f0804c08d75fcfab728a4f3d8331e53cca1968c253f5343b5d2b6b9d 18.771929136 735229 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": 160584, 
  "vin": [ {
      "gen": {
        "height": 160566
      }
    }
  ], 
  "vout": [ {
      "amount": 18771929136, 
      "target": {
        "key": "e86d57d1f0804c08d75fcfab728a4f3d8331e53cca1968c253f5343b5d2b6b9d"
      }
    }
  ], 
  "extra": [ 1, 111, 40, 224, 200, 64, 125, 103, 45, 58, 109, 232, 54, 229, 251, 185, 226, 128, 236, 138, 12, 245, 159, 68, 118, 240, 121, 210, 230, 235, 217, 230, 14, 3, 33, 0, 228, 163, 141, 166, 149, 253, 230, 176, 54, 105, 149, 233, 6, 236, 20, 174, 66, 236, 191, 152, 179, 38, 90, 14, 29, 125, 61, 205, 58, 184, 150, 140, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 17, 166, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}