Transaction hash
b277e8cfb4dead25428ce8ec3ff827ef2ff08ec01d42ff2f99bb343b60ee38d1
Transaction prefix hash
90a148b47ad5b1e61ab3ee4c34938aea6398643b148f33f4a59d43e51819bf8a
Transaction public key
53f7d39f25be8115f9d9af591e567bc8c954d2b8842d3ff2c5b7c20b665e2a3d
| Timestamp: 1788167971 | Timestamp [UTC]: 2026-08-31 09:19:31 | Age [y:d:h:m:s]: 00:002:01:25:35 |
| Block: 126 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 1300 | RingCT/type: yes/0 |
Extra: 0153f7d39f25be8115f9d9af591e567bc8c954d2b8842d3ff2c5b7c20b665e2a3d |
||
1 output(s) for total of 0.035175917379 QWC
| stealth address | amount | amount idx | tag |
00: e677e124e715b20145913554ff758e488df84cd497683214eab662e2e2fbc3f7 |
0.035175917379 | 126 of 0 | <7f> |
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": 186,
"vin": [ {
"gen": {
"height": 126
}
}
],
"vout": [ {
"amount": 35175917379,
"target": {
"tagged_key": {
"key": "e677e124e715b20145913554ff758e488df84cd497683214eab662e2e2fbc3f7",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 83, 247, 211, 159, 37, 190, 129, 21, 249, 217, 175, 89, 30, 86, 123, 200, 201, 84, 210, 184, 132, 45, 63, 242, 197, 183, 194, 11, 102, 94, 42, 61
],
"rct_signatures": {
"type": 0
}
}