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: 98710a2bd6df95118dbb5b4baec099f72b3d707aab801209f4a967295694be42
Tx prefix hash: 6b0f2237c68f102bd582d8ce06250bb303a49e4cd0d3c58fbd526a32ed06c9b3
Tx public key: 612c5b196f809f06ffdbcb4d31b6cdcaca6212c1fdf058ed3aafbefa324b97f1
| Timestamp: 1779723012 | Timestamp [UTC]: 2026-05-25 15:30:12 | Age [y:d:h:m:s]: 00:014:10:05:45 |
| Block: 1792 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6094 | RingCT/type: yes/0 |
| Extra: 01612c5b196f809f06ffdbcb4d31b6cdcaca6212c1fdf058ed3aafbefa324b97f1020900000005ba6d17be00 | ||
1 output(s) for total of 35.064385057308 HMNY
| stealth address | amount | amount idx | tag |
| 00: d2d3c8538904462cf0a1f2ebcf0df40813557c53a4823b877feec65f587e01a6 | 35.064385057308 | 1981 of 0 | <d7> |
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": 1852,
"vin": [ {
"gen": {
"height": 1792
}
}
],
"vout": [ {
"amount": 35064385057308,
"target": {
"tagged_key": {
"key": "d2d3c8538904462cf0a1f2ebcf0df40813557c53a4823b877feec65f587e01a6",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 97, 44, 91, 25, 111, 128, 159, 6, 255, 219, 203, 77, 49, 182, 205, 202, 202, 98, 18, 193, 253, 240, 88, 237, 58, 175, 190, 250, 50, 75, 151, 241, 2, 9, 0, 0, 0, 5, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}