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: d8ba981349bc1d1ed059c33be65b8fdcf574ad22ef238437b3c8b1a6808da93d
Tx prefix hash: 2e9c8e09784ddd3eda66d7ca626f851c4e5424874670ec4f67ce52712cdf284e
Tx public key: ca78a6d55979f66387a3caacd9d438d803d337cccc80c5da68c768f6163be18e
| Timestamp: 1780037189 | Timestamp [UTC]: 2026-05-29 06:46:29 | Age [y:d:h:m:s]: 00:010:18:49:28 |
| Block: 4248 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3638 | RingCT/type: yes/0 |
| Extra: 01ca78a6d55979f66387a3caacd9d438d803d337cccc80c5da68c768f6163be18e02090000000326697be300 | ||
1 output(s) for total of 34.900511731808 HMNY
| stealth address | amount | amount idx | tag |
| 00: 60819a24ceb96a995e76d51e8dcb2a35b6cb26481e76666268c1450d42e024af | 34.900511731808 | 5303 of 0 | <b7> |
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": 4308,
"vin": [ {
"gen": {
"height": 4248
}
}
],
"vout": [ {
"amount": 34900511731808,
"target": {
"tagged_key": {
"key": "60819a24ceb96a995e76d51e8dcb2a35b6cb26481e76666268c1450d42e024af",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 202, 120, 166, 213, 89, 121, 246, 99, 135, 163, 202, 172, 217, 212, 56, 216, 3, 211, 55, 204, 204, 128, 197, 218, 104, 199, 104, 246, 22, 59, 225, 142, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}