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: f5a598ee4b900494dea757d9d5e0fe6ce9288a6f0e2ed414a57d1adb5de48293
Tx prefix hash: 58bb73c78250a5935750014f70ff03b4d4dbdec6e824918636cf679e0059b705
Tx public key: 3d195aa5a972b9c82f4a4cc9c5ee753e7f61c8da21b9909f6e7005a94300b2e6
| Timestamp: 1779630164 | Timestamp [UTC]: 2026-05-24 13:42:44 | Age [y:d:h:m:s]: 00:015:11:53:13 |
| Block: 863 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7023 | RingCT/type: yes/0 |
| Extra: 013d195aa5a972b9c82f4a4cc9c5ee753e7f61c8da21b9909f6e7005a94300b2e6020900000001ba6d17be00 | ||
1 output(s) for total of 35.126571721864 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4b9cbda2aeaef7fb32b9b1d214f253fee050c567400d5044e1cc1429dfbda6d4 | 35.126571721864 | 995 of 0 | <13> |
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": 923,
"vin": [ {
"gen": {
"height": 863
}
}
],
"vout": [ {
"amount": 35126571721864,
"target": {
"tagged_key": {
"key": "4b9cbda2aeaef7fb32b9b1d214f253fee050c567400d5044e1cc1429dfbda6d4",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 61, 25, 90, 165, 169, 114, 185, 200, 47, 74, 76, 201, 197, 238, 117, 62, 127, 97, 200, 218, 33, 185, 144, 159, 110, 112, 5, 169, 67, 0, 178, 230, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}