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: 496427629c6a68a2050f6e8796cc40c0260755a7be69ade1e9d9679891f73dd7
Tx prefix hash: b15fa5017e6abcc30172a05f9b76d956974b863e30a61dabbcbbaeac996e1cfe
Tx public key: 46fb4c69e6d90eeb83fd1b7c96c54bf814fe32234211966a1ad8c63f698b6825
| Timestamp: 1780979374 | Timestamp [UTC]: 2026-06-09 04:29:34 | Age [y:d:h:m:s]: 00:000:04:45:13 |
| Block: 8000 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 349 | RingCT/type: yes/0 |
| Extra: 0146fb4c69e6d90eeb83fd1b7c96c54bf814fe32234211966a1ad8c63f698b6825020900000001e49593ff00 | ||
1 output(s) for total of 34.660670811356 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d1448a84a609ca54f1527897ada7577f94f9a101a66588a1f7bbbe8fb1c24e7 | 34.660670811356 | 9918 of 0 | <09> |
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": 8060,
"vin": [ {
"gen": {
"height": 8000
}
}
],
"vout": [ {
"amount": 34660670811356,
"target": {
"tagged_key": {
"key": "2d1448a84a609ca54f1527897ada7577f94f9a101a66588a1f7bbbe8fb1c24e7",
"view_tag": "09"
}
}
}
],
"extra": [ 1, 70, 251, 76, 105, 230, 217, 14, 235, 131, 253, 27, 124, 150, 197, 75, 248, 20, 254, 50, 35, 66, 17, 150, 106, 26, 216, 198, 63, 105, 139, 104, 37, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}