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: d5139227997b2a4cda8ef371478b6db093ea91a098d0a8d9f796de4e7b2a2710
Tx prefix hash: 2d14736d93be7c0a9de29e96eb25deef77180064a78e20b867f1d56cc2f5f920
Tx public key: 8ab9b273b176be50e5082df5e06f6f5f0d78fccfc012d8bbf580abd0890cfc2e
| Timestamp: 1780682719 | Timestamp [UTC]: 2026-06-05 18:05:19 | Age [y:d:h:m:s]: 00:003:05:13:34 |
| Block: 5306 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2580 | RingCT/type: yes/0 |
| Extra: 018ab9b273b176be50e5082df5e06f6f5f0d78fccfc012d8bbf580abd0890cfc2e020900000001e49593ff00 | ||
1 output(s) for total of 34.830154323277 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7fd0788f40ea057bea245156e94a45b2f3214965bf4f30f1edc8d4fd43c1b279 | 34.830154323277 | 6733 of 0 | <63> |
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": 5366,
"vin": [ {
"gen": {
"height": 5306
}
}
],
"vout": [ {
"amount": 34830154323277,
"target": {
"tagged_key": {
"key": "7fd0788f40ea057bea245156e94a45b2f3214965bf4f30f1edc8d4fd43c1b279",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 138, 185, 178, 115, 177, 118, 190, 80, 229, 8, 45, 245, 224, 111, 111, 95, 13, 120, 252, 207, 192, 18, 216, 187, 245, 128, 171, 208, 137, 12, 252, 46, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}