Terra Classic transaction
1E83F60E00680FE38F9DBABFF5C4A482901F044CB7B1326CB720DDC40C10D176
- Reported execution
- Success (code 0)
- Block
- 30771837
- Timestamp (UTC)
- 2026-10-10T06:02:34.000Z
- Gas used / wanted
- 1583176 / 1747417
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 49.495587 LUNC
Executed LUNC and USTC movements
Native transfer events are interpreted when successful execution is established. A transaction can contain several legs, including fees, tax and module routing.
Event source: Structured logs. 3 supported native legs retained of 3 parsed. At most 100 legs are retained.
| Asset | Exact amount | Sender wallet | Recipient wallet | Movement evidence | Message index |
|---|---|---|---|---|---|
 LUNC | 49.495587 | terra12jlsn34a…r9s5yel90g | terra17xpfvakm…8c5lkaeqfa
| Transaction fee | 0 |
| LUNC | 48,773.993622 | terra12jlsn34a…r9s5yel90g | terra13nk3znj8…eykq7s3hud | Transfer event | 0 |
| LUNC | 146.32198 | terra13nk3znj8…eykq7s3hud | terra1e98felys…w23s5vq5gf | Transfer event | 0 |
Movement interpretation and limits
This interprets LUNC and USTC native transfer events, using one event representation to avoid double counting. Other denominations, CW20 transfers and every contract effect are not decoded. Missing or conflicting evidence remains partial or unavailable.
Tax and fee labels require executed payment evidence. Module routing does not establish a burn, and a wallet address does not establish its owner. Leg totals are not unique trading volume or a change in supply. These movements are distinct from the declared message requests and fee fields.
Message indexes are zero based. The transaction block and UTC time above apply to these rows. All six native-token decimal places are retained before display.
Message types (3)
Declared messages describe attempted actions. Completed native transfer events are interpreted separately above.
- /cosmwasm.wasm.v1.MsgExecuteContract
- /cosmwasm.wasm.v1.MsgExecuteContract
- /cosmwasm.wasm.v1.MsgExecuteContract
What the messages request
These summaries interpret declared top-level fields. They describe requests, not proof of completed transfers or account ownership. Only the supported native movement table above interprets resulting transfer events.
- Contract execution request by terra12jlsn34ampqfwcvhtsp2z0hjl3jur9s5yel90g to terra13nk3znj8s74ugzycaqsaxtdex54fnxmeazsv8nnk9rycjg7peykq7s3hud. Contract instructions, attached funds and resulting effects are not decoded here.
- Contract execution request by terra12jlsn34ampqfwcvhtsp2z0hjl3jur9s5yel90g to terra16hzl7lge3jjnlazvut2ypt7upk68z5dycc9rwy608fah8q0y3fuslkenzc. Contract instructions, attached funds and resulting effects are not decoded here.
- Contract execution request by terra12jlsn34ampqfwcvhtsp2z0hjl3jur9s5yel90g to terra12j3xuxx52cg045qk37ee4k4u4fsgvyuf8d89dh7c9mr706jvxdascahqej. Contract instructions, attached funds and resulting effects are not decoded here.
Memo
Empty memo.
Memos are untrusted sender-supplied text; they do not verify an identity or claim.
Source: configured Terra Classic LCD transaction record (columbus-5). Successful source read . This is a source observation, not independent consensus verification. Linked block coverage may be incomplete.
Verify transaction in Finder