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: 016c440149cb014da081f60600e1141ee3ff1dd01b450dc0a0a2429f5adfb04a
Tx prefix hash: 36fac38e10fb2301f3059fcc43f96340415c414708ecc3721b9cefb7963175f4
Tx public key: c61c314cab5f5b448b446e3aba298f56a7993ac7a2fe29e64b8e8d29e8c4558b
| Timestamp: 1779644447 | Timestamp [UTC]: 2026-05-24 17:40:47 | Age [y:d:h:m:s]: 00:015:07:06:00 |
| Block: 1432 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6454 | RingCT/type: yes/0 |
| Extra: 01c61c314cab5f5b448b446e3aba298f56a7993ac7a2fe29e64b8e8d29e8c4558b | ||
1 output(s) for total of 35.088470150776 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70aea0ebd1fbf3efef49b65d1b966260fd756e0df10a6d080cf2e23d17b1ab23 | 35.088470150776 | 1586 of 0 | <dc> |
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": 1492,
"vin": [ {
"gen": {
"height": 1432
}
}
],
"vout": [ {
"amount": 35088470150776,
"target": {
"tagged_key": {
"key": "70aea0ebd1fbf3efef49b65d1b966260fd756e0df10a6d080cf2e23d17b1ab23",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 198, 28, 49, 76, 171, 95, 91, 68, 139, 68, 110, 58, 186, 41, 143, 86, 167, 153, 58, 199, 162, 254, 41, 230, 75, 142, 141, 41, 232, 196, 85, 139
],
"rct_signatures": {
"type": 0
}
}