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: c079a933886ed284e3d991a5e66b1967c356d27e0b550a5240f250a168e42ad1
Tx prefix hash: a32317b581d366567dcb44fe588e4dc66dcfe3accb7c9b1017b18c25579d3640
Tx public key: 0832c20a442dd5f2928f98aa7863474bd7c213c7397e36aaedb1fb1069f68b0f
| Timestamp: 1779459918 | Timestamp [UTC]: 2026-05-22 14:25:18 | Age [y:d:h:m:s]: 00:017:13:25:40 |
| Block: 430 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7541 | RingCT/type: yes/0 |
| Extra: 010832c20a442dd5f2928f98aa7863474bd7c213c7397e36aaedb1fb1069f68b0f02090000001293369e7d00 | ||
1 output(s) for total of 35.155594134268 HMNY
| stealth address | amount | amount idx | tag |
| 00: 15e561f4d6a5b6bde2065b885c39408b0446b5a932847343f1d25f8abdcb208f | 35.155594134268 | 434 of 0 | <49> |
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": 490,
"vin": [ {
"gen": {
"height": 430
}
}
],
"vout": [ {
"amount": 35155594134268,
"target": {
"tagged_key": {
"key": "15e561f4d6a5b6bde2065b885c39408b0446b5a932847343f1d25f8abdcb208f",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 8, 50, 194, 10, 68, 45, 213, 242, 146, 143, 152, 170, 120, 99, 71, 75, 215, 194, 19, 199, 57, 126, 54, 170, 237, 177, 251, 16, 105, 246, 139, 15, 2, 9, 0, 0, 0, 18, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}