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: 4979b98ce93eb9f513f892e13a947719817428fc5ae4969723b76b1a1356ec64
Tx prefix hash: 85baeeadab59d81dbbd5cf48069538525c8ecb447bcfc3f5ec2b0da275a81303
Tx public key: 72e2871f78c94671d30ecbae2950ea66632deed28e36e426d1ee2c25135627d3
| Timestamp: 1780999623 | Timestamp [UTC]: 2026-06-09 10:07:03 | Age [y:d:h:m:s]: 00:000:04:41:52 |
| Block: 8416 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 226 | RingCT/type: yes/0 |
| Extra: 0172e2871f78c94671d30ecbae2950ea66632deed28e36e426d1ee2c25135627d3020900000001e49593ff00 | ||
1 output(s) for total of 34.624158301160 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3bc4060787eadfe413704d7413442adb747a04eaab71a49f4c92cc52c35426a8 | 34.624158301160 | 10402 of 0 | <3d> |
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": 8476,
"vin": [ {
"gen": {
"height": 8416
}
}
],
"vout": [ {
"amount": 34624158301160,
"target": {
"tagged_key": {
"key": "3bc4060787eadfe413704d7413442adb747a04eaab71a49f4c92cc52c35426a8",
"view_tag": "3d"
}
}
}
],
"extra": [ 1, 114, 226, 135, 31, 120, 201, 70, 113, 211, 14, 203, 174, 41, 80, 234, 102, 99, 45, 238, 210, 142, 54, 228, 38, 209, 238, 44, 37, 19, 86, 39, 211, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}