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: 12ad8de09d9a155965ca985e47f9ce482b56a98d7f8989a475131579654a4d99
Tx prefix hash: e34e5844055315286caa4de22309925d17f5707b1fb42129a25c9b5e6b9f6501
Tx public key: c5c5c0a17a9d1fa448a4ce4e9d7dd27fd75513e9d5c4b9eef7c4878487ac8d42
| Timestamp: 1779855751 | Timestamp [UTC]: 2026-05-27 04:22:31 | Age [y:d:h:m:s]: 00:012:21:13:26 |
| Block: 2613 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5273 | RingCT/type: yes/0 |
| Extra: 01c5c5c0a17a9d1fa448a4ce4e9d7dd27fd75513e9d5c4b9eef7c4878487ac8d4202090000000126697be300 | ||
1 output(s) for total of 35.009519488440 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a51064032372af9d5372972f2eb46484201da55c7914ab7b27b3ae19e6c0e77 | 35.009519488440 | 3077 of 0 | <22> |
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": 2673,
"vin": [ {
"gen": {
"height": 2613
}
}
],
"vout": [ {
"amount": 35009519488440,
"target": {
"tagged_key": {
"key": "0a51064032372af9d5372972f2eb46484201da55c7914ab7b27b3ae19e6c0e77",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 197, 197, 192, 161, 122, 157, 31, 164, 72, 164, 206, 78, 157, 125, 210, 127, 215, 85, 19, 233, 213, 196, 185, 238, 247, 196, 135, 132, 135, 172, 141, 66, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}