For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 4c6e4d5d8622da9e7d7a9b3d846b4c534e0af57807cf82ef617ab11616328d4f
Tx prefix hash: e6f76723d2a6be46b6fd4e3ede12aa3c2019ec7cef76f546cd67b77918161354
Tx public key: fd80e8a193a4f0c9d227824d1efa8bf1437a84884a87fcdb078ed7db41e6cd8d
| Timestamp: 1780322879 | Timestamp [UTC]: 2026-06-01 14:07:59 | Age [y:d:h:m:s]: 00:007:12:32:37 |
| Block: 5027 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2871 | RingCT/type: yes/0 |
| Extra: 01fd80e8a193a4f0c9d227824d1efa8bf1437a84884a87fcdb078ed7db41e6cd8d02090000005626697be300 | ||
1 output(s) for total of 34.848694149484 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2422de57cebfbc0f1dceb3461f88e389de2184fadee18200a7b55cdb79f505a3 | 34.848694149484 | 6400 of 0 | <38> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 5087,
"vin": [ {
"gen": {
"height": 5027
}
}
],
"vout": [ {
"amount": 34848694149484,
"target": {
"tagged_key": {
"key": "2422de57cebfbc0f1dceb3461f88e389de2184fadee18200a7b55cdb79f505a3",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 253, 128, 232, 161, 147, 164, 240, 201, 210, 39, 130, 77, 30, 250, 139, 241, 67, 122, 132, 136, 74, 135, 252, 219, 7, 142, 215, 219, 65, 230, 205, 141, 2, 9, 0, 0, 0, 86, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}