Transaction Details
Tx hash
c38deef98ba0e046b527c45459c1680063d79e0316d7e89e6a1e087633d378dc
Tx prefix hash
dbd7aa59a4f4cc0ed0861e5a53978bf17f85898b908e655725c0097e8cf8c19a
Tx public key
6c84ed5c83767a4a4df4fe2a9a6d9203b746f5a8bb4cca36e1ae6bda69d43d7f
Age [y:d:h:m:s]
04:297:12:25:47
Timestamp [UCT] (epoch)
2019-09-16 01:46:37 (1568598397)
Block
265018 (1234506 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
016c84ed5c83767a4a4df4fe2a9a6d9203b746f5a8bb4cca36e1ae6bda69d43d7f021100000e7600e01a4b00000000000000000003210049f38ca4732b07173668f0fffbf440634b933cd43d738402dd2de4d0cb8d4a96
Outputs
1 output(s) for total of 20.272310235 ARQ
stealth address amount amount idx
00: c72f50c7020fbda9cf9a3d633fb0c485d8ebadaeea2d571e375346f6c7c52d8f 20.272310235 1186377 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": 265036, 
  "vin": [ {
      "gen": {
        "height": 265018
      }
    }
  ], 
  "vout": [ {
      "amount": 20272310235, 
      "target": {
        "key": "c72f50c7020fbda9cf9a3d633fb0c485d8ebadaeea2d571e375346f6c7c52d8f"
      }
    }
  ], 
  "extra": [ 1, 108, 132, 237, 92, 131, 118, 122, 74, 77, 244, 254, 42, 154, 109, 146, 3, 183, 70, 245, 168, 187, 76, 202, 54, 225, 174, 107, 218, 105, 212, 61, 127, 2, 17, 0, 0, 14, 118, 0, 224, 26, 75, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 73, 243, 140, 164, 115, 43, 7, 23, 54, 104, 240, 255, 251, 244, 64, 99, 75, 147, 60, 212, 61, 115, 132, 2, 221, 45, 228, 208, 203, 141, 74, 150
  ], 
  "rct_signatures": {
    "type": 0
  }
}