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: 07fc0122f65a818015b26846dff6583e6dc78ce486a7d0485b4307056165ddd0
Tx prefix hash: 730e14671d9eeedb8b8a6508dfa87ad6e15605c2f466d5034be5b34ac0c73d77
Tx public key: 3e31cc8d74f570af583b4b8c1c56ea57bf91f83cd6c6e82738a2e3ab262000ac
| Timestamp: 1780047217 | Timestamp [UTC]: 2026-05-29 09:33:37 | Age [y:d:h:m:s]: 00:010:16:02:20 |
| Block: 4357 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3529 | RingCT/type: yes/0 |
| Extra: 013e31cc8d74f570af583b4b8c1c56ea57bf91f83cd6c6e82738a2e3ab262000ac02090000000326697be300 | ||
1 output(s) for total of 34.893256627763 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d47d6a477c88d84c7dfe75547ef729bdeb7e25a9bbffc658b3aceb1d4c999c8 | 34.893256627763 | 5448 of 0 | <0f> |
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": 4417,
"vin": [ {
"gen": {
"height": 4357
}
}
],
"vout": [ {
"amount": 34893256627763,
"target": {
"tagged_key": {
"key": "2d47d6a477c88d84c7dfe75547ef729bdeb7e25a9bbffc658b3aceb1d4c999c8",
"view_tag": "0f"
}
}
}
],
"extra": [ 1, 62, 49, 204, 141, 116, 245, 112, 175, 88, 59, 75, 140, 28, 86, 234, 87, 191, 145, 248, 60, 214, 198, 232, 39, 56, 162, 227, 171, 38, 32, 0, 172, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}