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: 383400330f260a209652a22769291dadb1a097730a2ce49c80ce3e29579af364
Tx prefix hash: d2e8591dd1832f924c7b9c9f43a119266dbc4a84b5d270a844d89cfe79873d40
Tx public key: 07bf815b1ff01dd30a5a25bd84c2eebd46c6a42b89fa0ae60acfb7b7d0e7d439
| Timestamp: 1779860731 | Timestamp [UTC]: 2026-05-27 05:45:31 | Age [y:d:h:m:s]: 00:012:19:50:26 |
| Block: 2680 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5206 | RingCT/type: yes/0 |
| Extra: 0107bf815b1ff01dd30a5a25bd84c2eebd46c6a42b89fa0ae60acfb7b7d0e7d43902090000000126697be300 | ||
1 output(s) for total of 35.005045820968 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84a7f70e5623886035cd674637696bc2974df81b790db149feddb32390f55836 | 35.005045820968 | 3160 of 0 | <90> |
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": 2740,
"vin": [ {
"gen": {
"height": 2680
}
}
],
"vout": [ {
"amount": 35005045820968,
"target": {
"tagged_key": {
"key": "84a7f70e5623886035cd674637696bc2974df81b790db149feddb32390f55836",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 7, 191, 129, 91, 31, 240, 29, 211, 10, 90, 37, 189, 132, 194, 238, 189, 70, 198, 164, 43, 137, 250, 10, 230, 10, 207, 183, 183, 208, 231, 212, 57, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}