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: 431d187eb66df70f4016865649d42d39176d454402e3f673ec312146ca625a1a
Tx prefix hash: 4d97b8d95f871704dd0a11d9409ced3582f6434c61cc1a8d9f68df15e3a8fbb7
Tx public key: c41c6475a894ede95251a8c34a79d66f72724b530c02eb0ad2726e9764d56913
| Timestamp: 1779935494 | Timestamp [UTC]: 2026-05-28 02:31:34 | Age [y:d:h:m:s]: 00:012:01:19:24 |
| Block: 3432 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4534 | RingCT/type: yes/0 |
| Extra: 01c41c6475a894ede95251a8c34a79d66f72724b530c02eb0ad2726e9764d5691302090000000226697be300 | ||
1 output(s) for total of 34.954873110369 HMNY
| stealth address | amount | amount idx | tag |
| 00: 885664f2509afe8b0defd2ba4ac212520a047b47cc27e9433c659124ee8dd29e | 34.954873110369 | 4149 of 0 | <75> |
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": 3492,
"vin": [ {
"gen": {
"height": 3432
}
}
],
"vout": [ {
"amount": 34954873110369,
"target": {
"tagged_key": {
"key": "885664f2509afe8b0defd2ba4ac212520a047b47cc27e9433c659124ee8dd29e",
"view_tag": "75"
}
}
}
],
"extra": [ 1, 196, 28, 100, 117, 168, 148, 237, 233, 82, 81, 168, 195, 74, 121, 214, 111, 114, 114, 75, 83, 12, 2, 235, 10, 210, 114, 110, 151, 100, 213, 105, 19, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}