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: f2863fbedf456c421cce2ac76deb55ed4bf50a6479b116bc76ff218824ba379f
Tx prefix hash: 50f7cb7664124eebba697b7211c00c8516c6e03061749e7d81abcaebe9823cb7
Tx public key: c1922adb26d966b38d746083a1d395d6b757f036bb78c7b13978ddaf81774912
| Timestamp: 1779794260 | Timestamp [UTC]: 2026-05-26 11:17:40 | Age [y:d:h:m:s]: 00:013:18:20:59 |
| Block: 2255 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5854 | RingCT/type: yes/0 |
| Extra: 01c1922adb26d966b38d746083a1d395d6b757f036bb78c7b13978ddaf8177491202090000000226697be300 | ||
1 output(s) for total of 35.033433253414 HMNY
| stealth address | amount | amount idx | tag |
| 00: 770c34432455f4f022a7b8e98898d740757c7882e098a1bab632dc1dfa59fcf4 | 35.033433253414 | 2617 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": 2315,
"vin": [ {
"gen": {
"height": 2255
}
}
],
"vout": [ {
"amount": 35033433253414,
"target": {
"tagged_key": {
"key": "770c34432455f4f022a7b8e98898d740757c7882e098a1bab632dc1dfa59fcf4",
"view_tag": "f1"
}
}
}
],
"extra": [ 1, 193, 146, 42, 219, 38, 217, 102, 179, 141, 116, 96, 131, 161, 211, 149, 214, 183, 87, 240, 54, 187, 120, 199, 177, 57, 120, 221, 175, 129, 119, 73, 18, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}