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: e0551756a58c17e87b910a3f2e705e3b3b6f3fed5edc4a8cb3f000e2fb467081
Tx prefix hash: b71eb77e16f7188c2d7f709ff7c880d3ddb6c0bfaeafe66d74bd98eb8dfde93a
Tx public key: 42b10890e05a25b259a2c42a64c1ea24a42fc8ced6767ad8736f466bb4336685
| Timestamp: 1779635224 | Timestamp [UTC]: 2026-05-24 15:07:04 | Age [y:d:h:m:s]: 00:015:10:28:53 |
| Block: 1069 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6817 | RingCT/type: yes/0 |
| Extra: 0142b10890e05a25b259a2c42a64c1ea24a42fc8ced6767ad8736f466bb4336685020900000001ba6d17be00 | ||
1 output(s) for total of 35.112772704373 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0bdebe18421084e7fe41810aa0c9b297d924f95a1cfee0750e0a064672988e49 | 35.112772704373 | 1207 of 0 | <df> |
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": 1129,
"vin": [ {
"gen": {
"height": 1069
}
}
],
"vout": [ {
"amount": 35112772704373,
"target": {
"tagged_key": {
"key": "0bdebe18421084e7fe41810aa0c9b297d924f95a1cfee0750e0a064672988e49",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 66, 177, 8, 144, 224, 90, 37, 178, 89, 162, 196, 42, 100, 193, 234, 36, 164, 47, 200, 206, 214, 118, 122, 216, 115, 111, 70, 107, 180, 51, 102, 133, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}