Transaction Details
Tx hash
2ae0b1108582b83e4dd96f9ae77baf1e4edd811edf2119cef331d4aaef71069d
Tx prefix hash
ca72a8b9eb3cc24d4fcdd6ba4bc25c41ef178b1c31e5b34844e096a72583d170
Tx public key
e3a0d058a8768b5e1fd630a1d24936a5926711c38b0d87f4448d7ab1103d40df
Age [y:d:h:m:s]
05:114:15:43:21
Timestamp [UCT] (epoch)
2019-07-28 12:29:06 (1564316946)
Block
229948 (1363273 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e3a0d058a8768b5e1fd630a1d24936a5926711c38b0d87f4448d7ab1103d40df032100a6ed7b2180606c4fe43f0e7515d809c836d65c44aa201c517b2ae3ca31ddef60021b0000000000000000000000000e057975fa00000000000000000000
Outputs
1 output(s) for total of 18.161062883 ARQ
stealth address amount amount idx
00: e7046cb3db5ae7e46042c14f405a1520ff6bfb05560a7a3eb3cea1b50e54170f 18.161062883 1072572 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": 229966, 
  "vin": [ {
      "gen": {
        "height": 229948
      }
    }
  ], 
  "vout": [ {
      "amount": 18161062883, 
      "target": {
        "key": "e7046cb3db5ae7e46042c14f405a1520ff6bfb05560a7a3eb3cea1b50e54170f"
      }
    }
  ], 
  "extra": [ 1, 227, 160, 208, 88, 168, 118, 139, 94, 31, 214, 48, 161, 210, 73, 54, 165, 146, 103, 17, 195, 139, 13, 135, 244, 68, 141, 122, 177, 16, 61, 64, 223, 3, 33, 0, 166, 237, 123, 33, 128, 96, 108, 79, 228, 63, 14, 117, 21, 216, 9, 200, 54, 214, 92, 68, 170, 32, 28, 81, 123, 42, 227, 202, 49, 221, 239, 96, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 14, 5, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}