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: 89cb1a026df6bbb6844dc008910b6460bc6f02111f540c693940201a1ba29029
Tx prefix hash: bfa791ecfd82d2a4d9350f47628209bd9e91bd6324671ffbb3bb4f6aaa1a70c6
Tx public key: f04d8d6b6aafc452745f8e7f8527a4cbff25892ccc0a59c3657e7685cbd8881c
| Timestamp: 1779986169 | Timestamp [UTC]: 2026-05-28 16:36:09 | Age [y:d:h:m:s]: 00:011:08:59:48 |
| Block: 3960 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3926 | RingCT/type: yes/0 |
| Extra: 01f04d8d6b6aafc452745f8e7f8527a4cbff25892ccc0a59c3657e7685cbd8881c02090000000826697be300 | ||
1 output(s) for total of 34.919688440335 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce99ee52ee66e08308e806331aa7e505680d993f25a7caba86ce6c4ca902b0ff | 34.919688440335 | 4878 of 0 | <8a> |
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": 4020,
"vin": [ {
"gen": {
"height": 3960
}
}
],
"vout": [ {
"amount": 34919688440335,
"target": {
"tagged_key": {
"key": "ce99ee52ee66e08308e806331aa7e505680d993f25a7caba86ce6c4ca902b0ff",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 240, 77, 141, 107, 106, 175, 196, 82, 116, 95, 142, 127, 133, 39, 164, 203, 255, 37, 137, 44, 204, 10, 89, 195, 101, 126, 118, 133, 203, 216, 136, 28, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}