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: 4dbcb45a9f243acc73a4d94073fb6c2c6c031f9dc011c8fe238f1c3732100062
Tx prefix hash: 917f7929d2ad8f8b76875a11c9e156c4962e2a696b98d9cbf747f1224cb229d9
Tx public key: d641d28eb07399b30aeb493bb0497d5ae833049203ff390df3feabb9194dd3d6
| Timestamp: 1780062298 | Timestamp [UTC]: 2026-05-29 13:44:58 | Age [y:d:h:m:s]: 00:010:13:04:50 |
| Block: 4539 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3381 | RingCT/type: yes/0 |
| Extra: 01d641d28eb07399b30aeb493bb0497d5ae833049203ff390df3feabb9194dd3d602090000000126697be300 | ||
1 output(s) for total of 34.881145962199 HMNY
| stealth address | amount | amount idx | tag |
| 00: b4d905a02187aae23526124b2a5517de074494374bb483b298949c2417336b2a | 34.881145962199 | 5694 of 0 | <67> |
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": 4599,
"vin": [ {
"gen": {
"height": 4539
}
}
],
"vout": [ {
"amount": 34881145962199,
"target": {
"tagged_key": {
"key": "b4d905a02187aae23526124b2a5517de074494374bb483b298949c2417336b2a",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 214, 65, 210, 142, 176, 115, 153, 179, 10, 235, 73, 59, 176, 73, 125, 90, 232, 51, 4, 146, 3, 255, 57, 13, 243, 254, 171, 185, 25, 77, 211, 214, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}