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: 0bfa298434af037bf1fde4f4e725502e0e4e844377e74b203d5e6985abaaab87
Tx prefix hash: 82ddad0dcf1226809a85451b8c0ee6aee998d79009ec4a726f13bb6acfa1c924
Tx public key: 18bf6deb9d1b3bc42b2bdeff333190856d1b53e84bc45bbc41cedc902066f65d
| Timestamp: 1780015039 | Timestamp [UTC]: 2026-05-29 00:37:19 | Age [y:d:h:m:s]: 00:011:00:58:38 |
| Block: 4117 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3769 | RingCT/type: yes/0 |
| Extra: 0118bf6deb9d1b3bc42b2bdeff333190856d1b53e84bc45bbc41cedc902066f65d02090000000326697be300 | ||
1 output(s) for total of 34.909233164737 HMNY
| stealth address | amount | amount idx | tag |
| 00: c68626e93df0a633fd69b480c8c10a1d920240291f7c3988dc19ee9d936e6568 | 34.909233164737 | 5132 of 0 | <ea> |
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": 4177,
"vin": [ {
"gen": {
"height": 4117
}
}
],
"vout": [ {
"amount": 34909233164737,
"target": {
"tagged_key": {
"key": "c68626e93df0a633fd69b480c8c10a1d920240291f7c3988dc19ee9d936e6568",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 24, 191, 109, 235, 157, 27, 59, 196, 43, 43, 222, 255, 51, 49, 144, 133, 109, 27, 83, 232, 75, 196, 91, 188, 65, 206, 220, 144, 32, 102, 246, 93, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}