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: 78e64bf5dd6eaac35d3980e47748ba686aa82acd766c383e8d0de67e31b2f298
Tx prefix hash: 370dba97ae4d3a936f3a18a6388f026222ca88e332f0cc11a46ee5af267ecc22
Tx public key: 726c6af39c5c893655f9f5964c501eda4c638afae5d151e9d62d5bb058be9cd7
| Timestamp: 1779717061 | Timestamp [UTC]: 2026-05-25 13:51:01 | Age [y:d:h:m:s]: 00:014:11:44:56 |
| Block: 1670 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6216 | RingCT/type: yes/0 |
| Extra: 01726c6af39c5c893655f9f5964c501eda4c638afae5d151e9d62d5bb058be9cd7020900000002ba6d17be00 | ||
1 output(s) for total of 35.102128975334 HMNY
| stealth address | amount | amount idx | tag |
| 00: da06b17e436df2d806b85d319a5c087c0b8bbc01b767458ba6cd7023985eaa2c | 35.102128975334 | 1834 of 0 | <10> |
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": 1730,
"vin": [ {
"gen": {
"height": 1670
}
}
],
"vout": [ {
"amount": 35102128975334,
"target": {
"tagged_key": {
"key": "da06b17e436df2d806b85d319a5c087c0b8bbc01b767458ba6cd7023985eaa2c",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 114, 108, 106, 243, 156, 92, 137, 54, 85, 249, 245, 150, 76, 80, 30, 218, 76, 99, 138, 250, 229, 209, 81, 233, 214, 45, 91, 176, 88, 190, 156, 215, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}