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: e5fc0a2b6117a1b4082f88278fd655e315c97f633a217b7482d6117443fd422a
Tx prefix hash: 12dd79e63b6a49e140e28690e1a4a9680c2c7ea91166da5b38dd830fc25588a9
Tx public key: 77a281e4a3ba26fec600cb6e564d86ba9cc1752787f435c4e8cdfd3a5e86bb19
| Timestamp: 1779638890 | Timestamp [UTC]: 2026-05-24 16:08:10 | Age [y:d:h:m:s]: 00:015:09:27:47 |
| Block: 1225 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6661 | RingCT/type: yes/0 |
| Extra: 0177a281e4a3ba26fec600cb6e564d86ba9cc1752787f435c4e8cdfd3a5e86bb19020900000001ba6d17be00 | ||
1 output(s) for total of 35.102326569947 HMNY
| stealth address | amount | amount idx | tag |
| 00: a294e27642b8b142c99d48533b9c8d9dd8e139d0644448d047d68fe63bd67ba2 | 35.102326569947 | 1369 of 0 | <c4> |
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": 1285,
"vin": [ {
"gen": {
"height": 1225
}
}
],
"vout": [ {
"amount": 35102326569947,
"target": {
"tagged_key": {
"key": "a294e27642b8b142c99d48533b9c8d9dd8e139d0644448d047d68fe63bd67ba2",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 119, 162, 129, 228, 163, 186, 38, 254, 198, 0, 203, 110, 86, 77, 134, 186, 156, 193, 117, 39, 135, 244, 53, 196, 232, 205, 253, 58, 94, 134, 187, 25, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}