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: 0ccae5f648179c8ad36e0023be0d09b14ed8dbad9a5c780acccb35e056f30dd6
Tx prefix hash: d6639e3081dfadd70f70ebc90028c1ad63bfe5977d8dd220fce9ee9a46a587c9
Tx public key: f81584a4fbce5a7f791ec0efb01eff6c93af9bf9721514e99da0757d38970dcd
| Timestamp: 1779905518 | Timestamp [UTC]: 2026-05-27 18:11:58 | Age [y:d:h:m:s]: 00:012:07:23:59 |
| Block: 3187 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4699 | RingCT/type: yes/0 |
| Extra: 01f81584a4fbce5a7f791ec0efb01eff6c93af9bf9721514e99da0757d38970dcd02090000000126697be300 | ||
1 output(s) for total of 34.976220169803 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38b192697576fcff90c69f05fc5c98e9b7780a2eaf662ec5037bf4fdee334dba | 34.976220169803 | 3815 of 0 | <e4> |
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": 3247,
"vin": [ {
"gen": {
"height": 3187
}
}
],
"vout": [ {
"amount": 34976220169803,
"target": {
"tagged_key": {
"key": "38b192697576fcff90c69f05fc5c98e9b7780a2eaf662ec5037bf4fdee334dba",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 248, 21, 132, 164, 251, 206, 90, 127, 121, 30, 192, 239, 176, 30, 255, 108, 147, 175, 155, 249, 114, 21, 20, 233, 157, 160, 117, 125, 56, 151, 13, 205, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}