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: a60de6114712e13162c322e40aa443de25c799c6527af29fa7707c6d9321f50d
Tx prefix hash: 956bfc799f6ae75c4a2c66afb9f3969d0134b1b580a4581ec50ec24a43bd1468
Tx public key: 621616d1ec8f62be5fa76fc45c57f3428123703c7e9347fa900c5870dcb40633
| Timestamp: 1779712375 | Timestamp [UTC]: 2026-05-25 12:32:55 | Age [y:d:h:m:s]: 00:014:12:13:52 |
| Block: 1588 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6298 | RingCT/type: yes/0 |
| Extra: 01621616d1ec8f62be5fa76fc45c57f3428123703c7e9347fa900c5870dcb40633020900000003ba6d17be00 | ||
1 output(s) for total of 35.078031246418 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d39174bc364154bb97c213c23ebc4bc967a93397a266137f0a83ab79d5d087e | 35.078031246418 | 1746 of 0 | <26> |
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": 1648,
"vin": [ {
"gen": {
"height": 1588
}
}
],
"vout": [ {
"amount": 35078031246418,
"target": {
"tagged_key": {
"key": "9d39174bc364154bb97c213c23ebc4bc967a93397a266137f0a83ab79d5d087e",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 98, 22, 22, 209, 236, 143, 98, 190, 95, 167, 111, 196, 92, 87, 243, 66, 129, 35, 112, 60, 126, 147, 71, 250, 144, 12, 88, 112, 220, 180, 6, 51, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}