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: c198fbbb0f4514e92488dd1035fa64e77499050da8d378661146b94166338a90
Tx prefix hash: 9c1e36cfa05e8b6f5201fbf21a25cd799adf211699489038bfe98a7ae0a37703
Tx public key: 5c8f5f339d2fe5845a4ba14ee6d696577c8a112c41c4efe097663bab22358abf
| Timestamp: 1779938767 | Timestamp [UTC]: 2026-05-28 03:26:07 | Age [y:d:h:m:s]: 00:011:23:23:41 |
| Block: 3465 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4434 | RingCT/type: yes/0 |
| Extra: 015c8f5f339d2fe5845a4ba14ee6d696577c8a112c41c4efe097663bab22358abf02090000000126697be300 | ||
1 output(s) for total of 34.952673030239 HMNY
| stealth address | amount | amount idx | tag |
| 00: 82768823c136f4f186cd6fcb68a7538c4187262e06f16238af6cd119cda650e3 | 34.952673030239 | 4182 of 0 | <50> |
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": 3525,
"vin": [ {
"gen": {
"height": 3465
}
}
],
"vout": [ {
"amount": 34952673030239,
"target": {
"tagged_key": {
"key": "82768823c136f4f186cd6fcb68a7538c4187262e06f16238af6cd119cda650e3",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 92, 143, 95, 51, 157, 47, 229, 132, 90, 75, 161, 78, 230, 214, 150, 87, 124, 138, 17, 44, 65, 196, 239, 224, 151, 102, 59, 171, 34, 53, 138, 191, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}