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: aec5ab54f8ae829f38322ff198162e67dd10f302d975bc0481e521c86b467af8
Tx prefix hash: e0fc460c8c294d11785e55577c03de6e723abc761bc0906ba30255107c87bcb8
Tx public key: 9712fc53f9c0d3290e998406ada74df034f3340bef1189384e81fb85b5600b37
| Timestamp: 1779437344 | Timestamp [UTC]: 2026-05-22 08:09:04 | Age [y:d:h:m:s]: 00:017:17:26:53 |
| Block: 161 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7725 | RingCT/type: yes/0 |
| Extra: 019712fc53f9c0d3290e998406ada74df034f3340bef1189384e81fb85b5600b37020900000001a662ed0300 | ||
1 output(s) for total of 35.173636298702 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38ea09731ba8b5823138c99c49a3286a1ac2942e5338520e4dc10d41bb643734 | 35.173636298702 | 157 of 0 | <4f> |
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": 221,
"vin": [ {
"gen": {
"height": 161
}
}
],
"vout": [ {
"amount": 35173636298702,
"target": {
"tagged_key": {
"key": "38ea09731ba8b5823138c99c49a3286a1ac2942e5338520e4dc10d41bb643734",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 151, 18, 252, 83, 249, 192, 211, 41, 14, 153, 132, 6, 173, 167, 77, 240, 52, 243, 52, 11, 239, 17, 137, 56, 78, 129, 251, 133, 181, 96, 11, 55, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}