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: e8b245656abb6ebd148add0d28478062f043041e73be2908f491d57644313884
Tx prefix hash: 7f8a236646383047d0a4a4e9d0628d3bbaf68b3d72b3e1fe9766326370555b66
Tx public key: 082fe10939349d0bac584feb88555c7b794e2d17e1263ff210802f471a48231b
| Timestamp: 1779888987 | Timestamp [UTC]: 2026-05-27 13:36:27 | Age [y:d:h:m:s]: 00:012:11:59:30 |
| Block: 3042 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4844 | RingCT/type: yes/0 |
| Extra: 01082fe10939349d0bac584feb88555c7b794e2d17e1263ff210802f471a48231b02090000000226697be300 | ||
1 output(s) for total of 34.980884548968 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb5d2c0e8669bb96b3d4f9cdbb2eeae397c2c4a103f4546649fb68ea2182512d | 34.980884548968 | 3616 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": 3102,
"vin": [ {
"gen": {
"height": 3042
}
}
],
"vout": [ {
"amount": 34980884548968,
"target": {
"tagged_key": {
"key": "eb5d2c0e8669bb96b3d4f9cdbb2eeae397c2c4a103f4546649fb68ea2182512d",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 8, 47, 225, 9, 57, 52, 157, 11, 172, 88, 79, 235, 136, 85, 92, 123, 121, 78, 45, 23, 225, 38, 63, 242, 16, 128, 47, 71, 26, 72, 35, 27, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}