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: 40ecc74c475257668ea0f0c2f88edab577f07fd3f7178a73b742ca93aac08f61
Tx prefix hash: 295df749000ddb91d36f41f5dd5a1b199d8e361a5fffbd2bb6ea0282e72469d5
Tx public key: cc5e3097134bcae0fabf5e50afb02b2a0de389d5c356a6ecf74dc165c0266910
| Timestamp: 1781013969 | Timestamp [UTC]: 2026-06-09 14:06:09 | Age [y:d:h:m:s]: 00:007:18:57:48 |
| Block: 8612 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 133 | RingCT/type: yes/0 |
| Extra: 01cc5e3097134bcae0fabf5e50afb02b2a0de389d5c356a6ecf74dc165c0266910020900000001e49593ff00 | ||
1 output(s) for total of 34.611216801161 HMNY
| stealth address | amount | amount idx | tag |
| 00: 26cc04296975c381cd127d67eec631f80de30dd1b314484777be8698788c4dcd | 34.611216801161 | 10644 of 0 | <8d> |
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": 8672,
"vin": [ {
"gen": {
"height": 8612
}
}
],
"vout": [ {
"amount": 34611216801161,
"target": {
"tagged_key": {
"key": "26cc04296975c381cd127d67eec631f80de30dd1b314484777be8698788c4dcd",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 204, 94, 48, 151, 19, 75, 202, 224, 250, 191, 94, 80, 175, 176, 43, 42, 13, 227, 137, 213, 195, 86, 166, 236, 247, 77, 193, 101, 192, 38, 105, 16, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}