Transaction Details
Tx hash
d5b733e5cedd67fae5e7d5709d558e85d1ca20015d71c064e3b8fa7471611222
Tx prefix hash
bef118312d4da67788a961b17d1d3c62dae64c958d4c890b3467b4cbfd5ea473
Tx public key
1418b3cdb3276bf671df3e6ea6ef24114c8cc3b8d5a9d2d70948d0af1fd184a5
Age [y:d:h:m:s]
05:115:02:47:04
Timestamp [UCT] (epoch)
2019-08-06 21:31:35 (1565127095)
Block
236714 (1363497 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011418b3cdb3276bf671df3e6ea6ef24114c8cc3b8d5a9d2d70948d0af1fd184a5032100cbdd796d31a018efc82c153e29a0d3d840de03e661179e550c2281ad3c98578a021b00000000000000000000000003b8e9dd3400000000000000000000
Outputs
1 output(s) for total of 18.102542868 ARQ
stealth address amount amount idx
00: 1c443aa7a9a95a1cabfa39c2546f79e1c4edc097057a8d79f15a572c2aa3c809 18.102542868 1089975 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": 236732, 
  "vin": [ {
      "gen": {
        "height": 236714
      }
    }
  ], 
  "vout": [ {
      "amount": 18102542868, 
      "target": {
        "key": "1c443aa7a9a95a1cabfa39c2546f79e1c4edc097057a8d79f15a572c2aa3c809"
      }
    }
  ], 
  "extra": [ 1, 20, 24, 179, 205, 179, 39, 107, 246, 113, 223, 62, 110, 166, 239, 36, 17, 76, 140, 195, 184, 213, 169, 210, 215, 9, 72, 208, 175, 31, 209, 132, 165, 3, 33, 0, 203, 221, 121, 109, 49, 160, 24, 239, 200, 44, 21, 62, 41, 160, 211, 216, 64, 222, 3, 230, 97, 23, 158, 85, 12, 34, 129, 173, 60, 152, 87, 138, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 184, 233, 221, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}