Transaction hash
734c970f8668e0af8e9929acff3c9c0cf2454e9a5c8a92105578f7c1d422494b
Transaction prefix hash
c4925fc1b96c46706a00199b7f9a1bd9bc6669acedf4080afd689dbaf999beae
Transaction public key
57e2c7404a656fc8ba9909545e7878909837b409b06bb7091f73c0c55a25cca4
| Timestamp: 1788162974 | Timestamp [UTC]: 2026-08-31 07:56:14 | Age [y:d:h:m:s]: 00:002:01:46:55 |
| Block: 106 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 1166 | RingCT/type: yes/0 |
Extra: 0157e2c7404a656fc8ba9909545e7878909837b409b06bb7091f73c0c55a25cca4 |
||
1 output(s) for total of 0.035177259261 QWC
| stealth address | amount | amount idx | tag |
00: d4a3ae23b1755cb39c67fd519fa481ad9b8af0010d74939a57a152ad5d40fbf1 |
0.035177259261 | 106 of 0 | <69> |
Check which outputs belong to given Qwertycoin address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
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 Qwertycoin in this transaction
Tx private key can be obtained using get_tx_key
command in qwertycoin-wallet-cli command line tool
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": 166,
"vin": [ {
"gen": {
"height": 106
}
}
],
"vout": [ {
"amount": 35177259261,
"target": {
"tagged_key": {
"key": "d4a3ae23b1755cb39c67fd519fa481ad9b8af0010d74939a57a152ad5d40fbf1",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 87, 226, 199, 64, 74, 101, 111, 200, 186, 153, 9, 84, 94, 120, 120, 144, 152, 55, 180, 9, 176, 107, 183, 9, 31, 115, 192, 197, 90, 37, 204, 164
],
"rct_signatures": {
"type": 0
}
}