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: 71856726c45839ad83823ac320a7ffe2418af9a1e350f43c13ffd27f26b1034e
Tx prefix hash: 4d91579373a19335633ff591fddd03cadb5e455fda322ff191bc191f341365bd
Tx public key: b9c72d9b745873ff1d1a1eb0cbcab9231e041d3cffc5a56d8df8e806e479db5e
| Timestamp: 1780973393 | Timestamp [UTC]: 2026-06-09 02:49:53 | Age [y:d:h:m:s]: 00:000:09:47:52 |
| Block: 7899 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 681 | RingCT/type: yes/0 |
| Extra: 01b9c72d9b745873ff1d1a1eb0cbcab9231e041d3cffc5a56d8df8e806e479db5e020900000001e49593ff00 | ||
1 output(s) for total of 34.658318029707 HMNY
| stealth address | amount | amount idx | tag |
| 00: 25e331803699d797cb96780fa10ae6c7d28d43d9c54c04df5b83db3d53a41b02 | 34.658318029707 | 9797 of 0 | <57> |
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": 7959,
"vin": [ {
"gen": {
"height": 7899
}
}
],
"vout": [ {
"amount": 34658318029707,
"target": {
"tagged_key": {
"key": "25e331803699d797cb96780fa10ae6c7d28d43d9c54c04df5b83db3d53a41b02",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 185, 199, 45, 155, 116, 88, 115, 255, 29, 26, 30, 176, 203, 202, 185, 35, 30, 4, 29, 60, 255, 197, 165, 109, 141, 248, 232, 6, 228, 121, 219, 94, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}