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: d161e432965d205b2486f0a6eb018d3ed90a7536a8b87fa6f1f4e7868b4162e4
Tx prefix hash: 68c801c4e129103c0624982f7f8feeb833f0b16e99a087bdd3655f7278cdf9e9
Tx public key: b45af2ac0bc34dd8dc613c437fd9fd85b10f755e8b7e543003a75ba2beb6cc24
| Timestamp: 1780137420 | Timestamp [UTC]: 2026-05-30 10:37:00 | Age [y:d:h:m:s]: 00:009:14:09:47 |
| Block: 4973 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2913 | RingCT/type: yes/0 |
| Extra: 01b45af2ac0bc34dd8dc613c437fd9fd85b10f755e8b7e543003a75ba2beb6cc2402090000000326697be300 | ||
1 output(s) for total of 34.852283642651 HMNY
| stealth address | amount | amount idx | tag |
| 00: dad7d393f1f4bc0a20f5532e33aa1bd85dae2cdfba2f6bd4d8de19bf84d300f4 | 34.852283642651 | 6326 of 0 | <6c> |
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": 5033,
"vin": [ {
"gen": {
"height": 4973
}
}
],
"vout": [ {
"amount": 34852283642651,
"target": {
"tagged_key": {
"key": "dad7d393f1f4bc0a20f5532e33aa1bd85dae2cdfba2f6bd4d8de19bf84d300f4",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 180, 90, 242, 172, 11, 195, 77, 216, 220, 97, 60, 67, 127, 217, 253, 133, 177, 15, 117, 94, 139, 126, 84, 48, 3, 167, 91, 162, 190, 182, 204, 36, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}