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: 40073746c721b6854ab798d9876dda13588061c91d66d3adae7465e057dad691
Tx prefix hash: 5b62fe1db88e05a2106919266186bfe3611f80a0279a6138a4273612865ed053
Tx public key: 7b57348ada9ae9a413b9bfed1c7245b193985dc7c1bb68436cd4350fa6b9f819
| Timestamp: 1779734489 | Timestamp [UTC]: 2026-05-25 18:41:29 | Age [y:d:h:m:s]: 00:014:08:08:19 |
| Block: 1908 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5992 | RingCT/type: yes/0 |
| Extra: 017b57348ada9ae9a413b9bfed1c7245b193985dc7c1bb68436cd4350fa6b9f81902090000000226697be300 | ||
1 output(s) for total of 35.056627827295 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf8524d3d683106fed5e9f2c3d056911c19bf23aafb5538121f48d4e3e8c13b4 | 35.056627827295 | 2138 of 0 | <f7> |
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": 1968,
"vin": [ {
"gen": {
"height": 1908
}
}
],
"vout": [ {
"amount": 35056627827295,
"target": {
"tagged_key": {
"key": "bf8524d3d683106fed5e9f2c3d056911c19bf23aafb5538121f48d4e3e8c13b4",
"view_tag": "f7"
}
}
}
],
"extra": [ 1, 123, 87, 52, 138, 218, 154, 233, 164, 19, 185, 191, 237, 28, 114, 69, 177, 147, 152, 93, 199, 193, 187, 104, 67, 108, 212, 53, 15, 166, 185, 248, 25, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}