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: 21f6aeb4b444c2572ea9da5da4c8f8d5cef55c0a31fe2fc0fee6a4cb5abd6a66
Tx prefix hash: 98be8fdd9111af9d0d956b9432d7507ed8148761b0b7179eb813d22842b8faa9
Tx public key: b89e23d80164f800a302f55944d3e6da061739383c6592b7a5fc346291cde940
| Timestamp: 1779958124 | Timestamp [UTC]: 2026-05-28 08:48:44 | Age [y:d:h:m:s]: 00:016:02:32:21 |
| Block: 3723 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5022 | RingCT/type: yes/0 |
| Extra: 01b89e23d80164f800a302f55944d3e6da061739383c6592b7a5fc346291cde94002090000000226697be300 | ||
1 output(s) for total of 34.941191576448 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6c2080d6b5334ac2db14671165b17caa68353363a6c02f55fc4f6635850024cc | 34.941191576448 | 4506 of 0 | <42> |
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": 3783,
"vin": [ {
"gen": {
"height": 3723
}
}
],
"vout": [ {
"amount": 34941191576448,
"target": {
"tagged_key": {
"key": "6c2080d6b5334ac2db14671165b17caa68353363a6c02f55fc4f6635850024cc",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 184, 158, 35, 216, 1, 100, 248, 0, 163, 2, 245, 89, 68, 211, 230, 218, 6, 23, 57, 56, 60, 101, 146, 183, 165, 252, 52, 98, 145, 205, 233, 64, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}