Transaction Details
Tx hash
cd83fdbce36f217cded0e1ebe2bd9429864459df5884d0c97987e1eb2e9cba9e
Tx prefix hash
bb5aee9a5ec8b45192783f57e65e2fe145950f9e57241c3d2bea7ad92a1800d9
Tx public key
b3198151319afb75af30ee69a53a9458d30a62e5619fad40ca14a23db9ecf846
Age [y:d:h:m:s]
05:127:16:51:24
Timestamp [UCT] (epoch)
2019-07-27 16:57:52 (1564246672)
Block
229374 (1372516 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01b3198151319afb75af30ee69a53a9458d30a62e5619fad40ca14a23db9ecf8460321000ad8d15ac149fe0f5a0d3a9fad3a29aab2695c4e62f08cd0b95380496f28a7e9021b000000000000000000000000060a3771c800000000000000000000
Outputs
1 output(s) for total of 18.166034324 ARQ
stealth address amount amount idx
00: 9154a58e42a51c68971644564509fe9854c00fb3cc57efd2ba2bbb88a0ec3cf7 18.166034324 1070936 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": 229392, 
  "vin": [ {
      "gen": {
        "height": 229374
      }
    }
  ], 
  "vout": [ {
      "amount": 18166034324, 
      "target": {
        "key": "9154a58e42a51c68971644564509fe9854c00fb3cc57efd2ba2bbb88a0ec3cf7"
      }
    }
  ], 
  "extra": [ 1, 179, 25, 129, 81, 49, 154, 251, 117, 175, 48, 238, 105, 165, 58, 148, 88, 211, 10, 98, 229, 97, 159, 173, 64, 202, 20, 162, 61, 185, 236, 248, 70, 3, 33, 0, 10, 216, 209, 90, 193, 73, 254, 15, 90, 13, 58, 159, 173, 58, 41, 170, 178, 105, 92, 78, 98, 240, 140, 208, 185, 83, 128, 73, 111, 40, 167, 233, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 10, 55, 113, 200, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}