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: 8b42ee68f899ddeb6ce82cbe3666f5ba6c814d7c6104aa8c6e1e83da91d3a72b
Tx prefix hash: fd9ab14225989f8428647ffe47d6b79a7cbb4b0817690e8ece8dcee1ddfaa0c9
Tx public key: dcf0f45493ab19dd5be6eb588a8255cc1e3ca44e814f310c16be6b025faa6f07
| Timestamp: 1779465180 | Timestamp [UTC]: 2026-05-22 15:53:00 | Age [y:d:h:m:s]: 00:017:08:53:47 |
| Block: 495 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7391 | RingCT/type: yes/0 |
| Extra: 01dcf0f45493ab19dd5be6eb588a8255cc1e3ca44e814f310c16be6b025faa6f0702090000000293369e7d00 | ||
1 output(s) for total of 35.151235891943 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32eb29a3269543451fcb182eb297e6d1d881b47695edb659f44d77aa99060194 | 35.151235891943 | 499 of 0 | <cc> |
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": 555,
"vin": [ {
"gen": {
"height": 495
}
}
],
"vout": [ {
"amount": 35151235891943,
"target": {
"tagged_key": {
"key": "32eb29a3269543451fcb182eb297e6d1d881b47695edb659f44d77aa99060194",
"view_tag": "cc"
}
}
}
],
"extra": [ 1, 220, 240, 244, 84, 147, 171, 25, 221, 91, 230, 235, 88, 138, 130, 85, 204, 30, 60, 164, 78, 129, 79, 49, 12, 22, 190, 107, 2, 95, 170, 111, 7, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}