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: d89d41c13dcaa545a1dfb9c96ff7229aa11708496166f8834df61c9bf0ade4c1
Tx prefix hash: 8daa092db25ae89c86ce217a1b2112dc348bf4adc62d2e8172cee2733d7ef7a4
Tx public key: 8e63b5bc626e684524e69565aa687b8d772f5bd01f4f3294db599ad1bd3b6c5f
| Timestamp: 1780982686 | Timestamp [UTC]: 2026-06-09 05:24:46 | Age [y:d:h:m:s]: 00:000:08:12:50 |
| Block: 8069 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 531 | RingCT/type: yes/0 |
| Extra: 018e63b5bc626e684524e69565aa687b8d772f5bd01f4f3294db599ad1bd3b6c5f020900000001e49593ff00 | ||
1 output(s) for total of 34.647081906505 HMNY
| stealth address | amount | amount idx | tag |
| 00: 79e7fc7aff20b28f92ff5b1e1d9f3a2564b83655b5f9dd1475db15c7837114e1 | 34.647081906505 | 9999 of 0 | <79> |
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": 8129,
"vin": [ {
"gen": {
"height": 8069
}
}
],
"vout": [ {
"amount": 34647081906505,
"target": {
"tagged_key": {
"key": "79e7fc7aff20b28f92ff5b1e1d9f3a2564b83655b5f9dd1475db15c7837114e1",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 142, 99, 181, 188, 98, 110, 104, 69, 36, 230, 149, 101, 170, 104, 123, 141, 119, 47, 91, 208, 31, 79, 50, 148, 219, 89, 154, 209, 189, 59, 108, 95, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}