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: 6d773ca5171fab73686692a1ce3a6ccbe411c677925797bd4e6257fac1021973
Tx prefix hash: fe171866207bdbcc58f43f7a6cd424b4b3b528f1fed9355a21e43864ef09a9fb
Tx public key: ae0034ca02bf4792ca3b04a1648612931be88ab32bf006b205943ab210b8e928
| Timestamp: 1780822294 | Timestamp [UTC]: 2026-06-07 08:51:34 | Age [y:d:h:m:s]: 00:001:16:44:23 |
| Block: 7198 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 688 | RingCT/type: yes/0 |
| Extra: 01ae0034ca02bf4792ca3b04a1648612931be88ab32bf006b205943ab210b8e928020900000002e49593ff00 | ||
1 output(s) for total of 34.704689019572 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36fa30587240ec50d64d601bc392846d6d80fa8bbe34e11f9095d63925587b85 | 34.704689019572 | 8866 of 0 | <c6> |
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": 7258,
"vin": [ {
"gen": {
"height": 7198
}
}
],
"vout": [ {
"amount": 34704689019572,
"target": {
"tagged_key": {
"key": "36fa30587240ec50d64d601bc392846d6d80fa8bbe34e11f9095d63925587b85",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 174, 0, 52, 202, 2, 191, 71, 146, 202, 59, 4, 161, 100, 134, 18, 147, 27, 232, 138, 179, 43, 240, 6, 178, 5, 148, 58, 178, 16, 184, 233, 40, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}