Transaction hash
36130fab939175c2b57a914bb6dac5037e6f97ce7f6d93320d5d0a4abfd9ce14
Transaction prefix hash
da34b1d44e23da39899f6ffa1db657bf57afc34d5651d36eef93db4aa939fb48
Transaction public key
8a9147d9fb041c2353b26c8e93bcb0e84a38577b4bb819c3cf22b3b21005dcbd
| Timestamp: 1788162973 | Timestamp [UTC]: 2026-08-31 07:56:13 | Age [y:d:h:m:s]: 00:002:03:50:34 |
| Block: 104 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 1341 | RingCT/type: yes/0 |
Extra: 018a9147d9fb041c2353b26c8e93bcb0e84a38577b4bb819c3cf22b3b21005dcbd |
||
1 output(s) for total of 0.035177393452 QWC
| stealth address | amount | amount idx | tag |
00: c0b1d57e4b36629f86b465f4aedd3898760b3c53248b175d944921ae7349dd22 |
0.035177393452 | 104 of 0 | <bc> |
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": 164,
"vin": [ {
"gen": {
"height": 104
}
}
],
"vout": [ {
"amount": 35177393452,
"target": {
"tagged_key": {
"key": "c0b1d57e4b36629f86b465f4aedd3898760b3c53248b175d944921ae7349dd22",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 138, 145, 71, 217, 251, 4, 28, 35, 83, 178, 108, 142, 147, 188, 176, 232, 74, 56, 87, 123, 75, 184, 25, 195, 207, 34, 179, 178, 16, 5, 220, 189
],
"rct_signatures": {
"type": 0
}
}