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: 4be8d47659798da0e894085cd72c0ff1b86947ac796bc17f16f09135e321a1a8
Tx prefix hash: 1909e933917e8d7e9b810723bb3f56c0fca77d03bbe03d82dee34d651f2b7167
Tx public key: 087f19ed20342c66dc7dc3961ccb4bebc7200bafe0cc0514e7d4d23cd2993636
| Timestamp: 1779890239 | Timestamp [UTC]: 2026-05-27 13:57:19 | Age [y:d:h:m:s]: 00:012:11:38:38 |
| Block: 3055 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4831 | RingCT/type: yes/0 |
| Extra: 01087f19ed20342c66dc7dc3961ccb4bebc7200bafe0cc0514e7d4d23cd299363602090000000226697be300 | ||
1 output(s) for total of 34.980017189244 HMNY
| stealth address | amount | amount idx | tag |
| 00: df2942aff20170c5a55f0ad1ac4529dbe9c3e74bee78354291665b3ba0ba5af7 | 34.980017189244 | 3633 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": 3115,
"vin": [ {
"gen": {
"height": 3055
}
}
],
"vout": [ {
"amount": 34980017189244,
"target": {
"tagged_key": {
"key": "df2942aff20170c5a55f0ad1ac4529dbe9c3e74bee78354291665b3ba0ba5af7",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 8, 127, 25, 237, 32, 52, 44, 102, 220, 125, 195, 150, 28, 203, 75, 235, 199, 32, 11, 175, 224, 204, 5, 20, 231, 212, 210, 60, 210, 153, 54, 54, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}