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: f26191de2bce8a30ad506d6693b7997e316fb5edb8d5cba8d9e91a0c80b0ade0
Tx prefix hash: 9feab2a8dc5e4af9859a8788b5640d69c317d15d3c9f9579e65099beb6aa3883
Tx public key: 8b13caea121c99406cd29bcbbd54f0a273b27ad12e0fa2b984dd05e6af1618ed
| Timestamp: 1779633855 | Timestamp [UTC]: 2026-05-24 14:44:15 | Age [y:d:h:m:s]: 00:015:11:56:21 |
| Block: 1006 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6890 | RingCT/type: yes/0 |
| Extra: 018b13caea121c99406cd29bcbbd54f0a273b27ad12e0fa2b984dd05e6af1618ed020900000001ba6d17be00 | ||
1 output(s) for total of 35.116992216744 HMNY
| stealth address | amount | amount idx | tag |
| 00: c89ff1fd21bb87c183b2ab9d22c5cbac79808d098e6137084cc35583f240a154 | 35.116992216744 | 1142 of 0 | <98> |
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": 1066,
"vin": [ {
"gen": {
"height": 1006
}
}
],
"vout": [ {
"amount": 35116992216744,
"target": {
"tagged_key": {
"key": "c89ff1fd21bb87c183b2ab9d22c5cbac79808d098e6137084cc35583f240a154",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 139, 19, 202, 234, 18, 28, 153, 64, 108, 210, 155, 203, 189, 84, 240, 162, 115, 178, 122, 209, 46, 15, 162, 185, 132, 221, 5, 230, 175, 22, 24, 237, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}