Transaction Details
Tx hash
27a76c9b1fdf61759fba26dce26bd02942dd22004d02469ca1a8e43cb6a340e0
Tx prefix hash
a7f1ae703da74f04e806b339fb2724023946c9fe0ab8b192f9d97e33f53c80c4
Tx public key
4e3cdc1e2b14957c1d54740e8eb213ca1b0bb2351c1d0d886c722edf5b5ac23e
Age [y:d:h:m:s]
05:185:10:48:43
Timestamp [UCT] (epoch)
2019-05-18 20:11:45 (1558210305)
Block
179324 (1413990 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014e3cdc1e2b14957c1d54740e8eb213ca1b0bb2351c1d0d886c722edf5b5ac23e032100e2b573e23a9796b9599f419f53dacf7c0ad01084caec148285ec3a1d04a3e774021b000000000000000000000000003c01d3b100000000000000000000
Outputs
1 output(s) for total of 18.604772045 ARQ
stealth address amount amount idx
00: 6902a0b4e00f86f8d8c45527bb0caeb1a971387312066b00dbe6c3956c3d585f 18.604772045 808776 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": 179342, 
  "vin": [ {
      "gen": {
        "height": 179324
      }
    }
  ], 
  "vout": [ {
      "amount": 18604772045, 
      "target": {
        "key": "6902a0b4e00f86f8d8c45527bb0caeb1a971387312066b00dbe6c3956c3d585f"
      }
    }
  ], 
  "extra": [ 1, 78, 60, 220, 30, 43, 20, 149, 124, 29, 84, 116, 14, 142, 178, 19, 202, 27, 11, 178, 53, 28, 29, 13, 136, 108, 114, 46, 223, 91, 90, 194, 62, 3, 33, 0, 226, 181, 115, 226, 58, 151, 150, 185, 89, 159, 65, 159, 83, 218, 207, 124, 10, 208, 16, 132, 202, 236, 20, 130, 133, 236, 58, 29, 4, 163, 231, 116, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 60, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}