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: 91067c2172666d9270f681c87de55d3f516dda2bdd539e8501251836feb10e1f
Tx prefix hash: 487ac16cbe527fc78d83ee29f3adcafee69932402cc8f919097e52ef3eda4fed
Tx public key: 4aab780fe9e156a29f6df6d9838be19a654ac4d2aca89483a09a39f36dc57831
| Timestamp: 1780137747 | Timestamp [UTC]: 2026-05-30 10:42:27 | Age [y:d:h:m:s]: 00:009:14:53:30 |
| Block: 4975 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2911 | RingCT/type: yes/0 |
| Extra: 014aab780fe9e156a29f6df6d9838be19a654ac4d2aca89483a09a39f36dc5783102090000000526697be300 | ||
1 output(s) for total of 34.852150691866 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8087d4d19205c57cb13a505e58ebd2393d4cf22273d4c23368dde67a5e827e6c | 34.852150691866 | 6330 of 0 | <db> |
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": 5035,
"vin": [ {
"gen": {
"height": 4975
}
}
],
"vout": [ {
"amount": 34852150691866,
"target": {
"tagged_key": {
"key": "8087d4d19205c57cb13a505e58ebd2393d4cf22273d4c23368dde67a5e827e6c",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 74, 171, 120, 15, 233, 225, 86, 162, 159, 109, 246, 217, 131, 139, 225, 154, 101, 74, 196, 210, 172, 168, 148, 131, 160, 154, 57, 243, 109, 197, 120, 49, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}