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: e53237476eee22063f9c573f785cd2b2cf18454015170ee78bac6085b2b88d83
Tx prefix hash: 8889ac8555ead9fcacfa5091a4f84e0e6e0d9db723f8a8232065788028e61c96
Tx public key: 265336d420c0223cb6f63c35df75efe252a7c8eba318cf914231a7413c8f5cb5
| Timestamp: 1779853496 | Timestamp [UTC]: 2026-05-27 03:44:56 | Age [y:d:h:m:s]: 00:013:00:06:02 |
| Block: 2569 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5418 | RingCT/type: yes/0 |
| Extra: 01265336d420c0223cb6f63c35df75efe252a7c8eba318cf914231a7413c8f5cb502090000000126697be300 | ||
1 output(s) for total of 35.012457730336 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5d724902b3e61106a0231455dedd5204dc6c73cd08e94990f30b3e35cd8a2d89 | 35.012457730336 | 3025 of 0 | <c6> |
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": 2629,
"vin": [ {
"gen": {
"height": 2569
}
}
],
"vout": [ {
"amount": 35012457730336,
"target": {
"tagged_key": {
"key": "5d724902b3e61106a0231455dedd5204dc6c73cd08e94990f30b3e35cd8a2d89",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 38, 83, 54, 212, 32, 192, 34, 60, 182, 246, 60, 53, 223, 117, 239, 226, 82, 167, 200, 235, 163, 24, 207, 145, 66, 49, 167, 65, 60, 143, 92, 181, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}