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: 85eb453e26feb3b0aaf7511979e39d6265bd1ea0e27474093d26589bd7685971
Tx prefix hash: de0627385309c3d93b7f8ca7bf11556476345958c8c6cee3f7b4050c312d45b5
Tx public key: df2b5fc9b8815cdf77de761e9dc4242ce90fb9eda8b051ea169d9a3cabf08bf4
| Timestamp: 1779455258 | Timestamp [UTC]: 2026-05-22 13:07:38 | Age [y:d:h:m:s]: 00:017:10:11:15 |
| Block: 377 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7509 | RingCT/type: yes/0 |
| Extra: 01df2b5fc9b8815cdf77de761e9dc4242ce90fb9eda8b051ea169d9a3cabf08bf402090000000893369e7d00 | ||
1 output(s) for total of 35.240040177936 HMNY
| stealth address | amount | amount idx | tag |
| 00: df80961a3565d0f2e07671e70300f8e1f7a4f88d46055c0443ed90d591999fc4 | 35.240040177936 | 373 of 0 | <41> |
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": 437,
"vin": [ {
"gen": {
"height": 377
}
}
],
"vout": [ {
"amount": 35240040177936,
"target": {
"tagged_key": {
"key": "df80961a3565d0f2e07671e70300f8e1f7a4f88d46055c0443ed90d591999fc4",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 223, 43, 95, 201, 184, 129, 92, 223, 119, 222, 118, 30, 157, 196, 36, 44, 233, 15, 185, 237, 168, 176, 81, 234, 22, 157, 154, 60, 171, 240, 139, 244, 2, 9, 0, 0, 0, 8, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}