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: 563db32de4833f2e88a7707ae8b7b5a259c81b2a89c385906b9da87f927d8a2e
Tx prefix hash: f068b9d6c3c2c89060e5ec2bf9b6fe7170a09cc5f84d1e4cd7240a70b5bc9463
Tx public key: 98f835af5ea17ae01a97e194a85eaedd798eeac6ac451d9a757405fd7115a5bf
| Timestamp: 1779473149 | Timestamp [UTC]: 2026-05-22 18:05:49 | Age [y:d:h:m:s]: 00:017:07:30:08 |
| Block: 588 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7298 | RingCT/type: yes/0 |
| Extra: 0198f835af5ea17ae01a97e194a85eaedd798eeac6ac451d9a757405fd7115a5bf02090000000793369e7d00 | ||
1 output(s) for total of 35.145001192439 HMNY
| stealth address | amount | amount idx | tag |
| 00: a80bf04dd2aebedb0fe4ecdf3ac5fc5e5b29e914aef3d6a1fe81eae5b40e9ccc | 35.145001192439 | 600 of 0 | <3f> |
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": 648,
"vin": [ {
"gen": {
"height": 588
}
}
],
"vout": [ {
"amount": 35145001192439,
"target": {
"tagged_key": {
"key": "a80bf04dd2aebedb0fe4ecdf3ac5fc5e5b29e914aef3d6a1fe81eae5b40e9ccc",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 152, 248, 53, 175, 94, 161, 122, 224, 26, 151, 225, 148, 168, 94, 174, 221, 121, 142, 234, 198, 172, 69, 29, 154, 117, 116, 5, 253, 113, 21, 165, 191, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}