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: e104152934bc715c4ca4f4f68bb663e42b62ed71ded2abca82488576d0bccf90
Tx prefix hash: ece3925e0a66d3b687b35e75d0d8f43fbf0b5cd1d99314f3bd1e0271a65cc8b7
Tx public key: 104e90603008e548f55c1f622580276c4f270d4478755ec9943cef26f778bf58
| Timestamp: 1779722733 | Timestamp [UTC]: 2026-05-25 15:25:33 | Age [y:d:h:m:s]: 00:014:06:59:16 |
| Block: 1785 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6101 | RingCT/type: yes/0 |
| Extra: 01104e90603008e548f55c1f622580276c4f270d4478755ec9943cef26f778bf58020900000002ba6d17be00 | ||
1 output(s) for total of 35.064853220928 HMNY
| stealth address | amount | amount idx | tag |
| 00: e461d215948e6d7a53b52e99b206b9ad596c51032f24847e04ce7290f8747397 | 35.064853220928 | 1972 of 0 | <f1> |
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": 1845,
"vin": [ {
"gen": {
"height": 1785
}
}
],
"vout": [ {
"amount": 35064853220928,
"target": {
"tagged_key": {
"key": "e461d215948e6d7a53b52e99b206b9ad596c51032f24847e04ce7290f8747397",
"view_tag": "f1"
}
}
}
],
"extra": [ 1, 16, 78, 144, 96, 48, 8, 229, 72, 245, 92, 31, 98, 37, 128, 39, 108, 79, 39, 13, 68, 120, 117, 94, 201, 148, 60, 239, 38, 247, 120, 191, 88, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}