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: 1c38300fa048b9675219fb57ca29f903ae4f44084426e11605ad958676d78c29
Tx prefix hash: a3c17d892c93389b8a32c13f234217ec63e0e5331dd2ffde884a4b54688b01dd
Tx public key: 13bfab9420bfed3ab7c24cb464d4f2a91d2e8f50849a0530ac5cee9037f1d37d
| Timestamp: 1780065272 | Timestamp [UTC]: 2026-05-29 14:34:32 | Age [y:d:h:m:s]: 00:010:12:15:16 |
| Block: 4576 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3333 | RingCT/type: yes/0 |
| Extra: 0113bfab9420bfed3ab7c24cb464d4f2a91d2e8f50849a0530ac5cee9037f1d37d02090000000326697be300 | ||
1 output(s) for total of 34.878684417986 HMNY
| stealth address | amount | amount idx | tag |
| 00: a4634df23df888ff627366e269eb713737f4b518cf49debf395a345292c31fe9 | 34.878684417986 | 5744 of 0 | <a2> |
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": 4636,
"vin": [ {
"gen": {
"height": 4576
}
}
],
"vout": [ {
"amount": 34878684417986,
"target": {
"tagged_key": {
"key": "a4634df23df888ff627366e269eb713737f4b518cf49debf395a345292c31fe9",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 19, 191, 171, 148, 32, 191, 237, 58, 183, 194, 76, 180, 100, 212, 242, 169, 29, 46, 143, 80, 132, 154, 5, 48, 172, 92, 238, 144, 55, 241, 211, 125, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}