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: af4f333e7b269ccfd2999ea2ec1dd2ca91a7e991aab03b796f22748a4b96a620
Tx prefix hash: 8a93db0aa0537f19218bcce6ec416df122bab557fa5834be6c15dba9c62fc66e
Tx public key: faa65cba6a09ed87ed0263221f8689f73524d83a2ee9987d5cf9fad353b9958d
| Timestamp: 1779459593 | Timestamp [UTC]: 2026-05-22 14:19:53 | Age [y:d:h:m:s]: 00:017:12:20:43 |
| Block: 427 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7469 | RingCT/type: yes/0 |
| Extra: 01faa65cba6a09ed87ed0263221f8689f73524d83a2ee9987d5cf9fad353b9958d02090000000793369e7d00 | ||
1 output(s) for total of 35.155795296958 HMNY
| stealth address | amount | amount idx | tag |
| 00: 66f891b7609a3d27f2711082324f20131e11540539ab97a706e36ed4b37b9ae4 | 35.155795296958 | 431 of 0 | <63> |
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": 487,
"vin": [ {
"gen": {
"height": 427
}
}
],
"vout": [ {
"amount": 35155795296958,
"target": {
"tagged_key": {
"key": "66f891b7609a3d27f2711082324f20131e11540539ab97a706e36ed4b37b9ae4",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 250, 166, 92, 186, 106, 9, 237, 135, 237, 2, 99, 34, 31, 134, 137, 247, 53, 36, 216, 58, 46, 233, 152, 125, 92, 249, 250, 211, 83, 185, 149, 141, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}