Terra Classic transaction
8C33F0F65A266D336C609DD005628319A6A0A682591628DB83B189D0D08EC157
- Reported execution
- Success (code 0)
- Block
- 30773493
- Timestamp (UTC)
- 2026-10-10T08:45:59.000Z
- Gas used / wanted
- 541834 / 560000
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 15.862 LUNC
- Declared gas limit
- 560000
- Declared fee payer
- Empty payer field; signer address not resolved here.
- Declared fee granter
- Empty granter field; no fee grant requested in this field.
These are declarations in the returned transaction. A granter names a requested fee grant; it does not prove a grant existed or paid. The declared gas limit is separate from reported gas wanted and gas used. These fields do not establish signer identity, actual debits, tax, refunds or burns.
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. 1 supported native legs retained of 1 parsed. At most 100 legs are retained.
| Asset | Exact amount | Sender wallet | Recipient wallet | Movement evidence | Message index |
|---|---|---|---|---|---|
 LUNC | 15.862 | terra12z8vz3vg…95yqsdtjj3 | terra17xpfvakm…8c5lkaeqfa
| Transaction fee | 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.
Contract-reported transfers
CW20-style transfer events from this transaction. Quantities retain their exact raw units. Contract code, historical token decimals, balances and wallet ownership are not independently verified by these events.
2 eligible events shown; complete supported count unavailable.
Some contract event fields were ambiguous or unsupported; a complete supported event count is unavailable.
Transfer · message 1
- Reporting contract
- terra1f0eqgy9w7e5e7up97vjudqwx38tesf8ylx75x2lv3nwm0clry0pqmgfy72
- Reported raw quantity
- 5000000
- Base units; historical decimals unavailable
Transfer · message 1
- Reporting contract
- terra1cvd5cgrs8rrl96hte34n57497u5f9cwuv3e6ztxgetkx4uzmcdyswv79zl
- Reported raw quantity
- 4935772
- Base units; historical decimals unavailable
Addresses identify roles reported by the contract. Repeated operations remain separate; quantities are not added across token contracts. This view covers transfers and sends, including allowance actions. Token creation, token burns and other contract effects remain outside this view.
Contract-reported mints and burns
CW20-style token events reported by contracts in this transaction. Quantities retain exact raw units. These are not native LUNC or USTC burns, and they are not added to native burn totals.
0 supported events in the selected message logs.
No supported CW20-style mint or burn events were present in the selected representation.
Contract code, historical token decimals, balances, authority and ownership are not independently verified. Events do not establish before-and-after supply, redemption or destination-chain settlement. Each operation remains separate; no cross-contract total or inferred counterparty is shown.
Message types (1)
Declared messages describe attempted actions. Native movements and contract-reported token events are shown in the event panels above.
- /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. The event panels above show supported native movements and contract-reported token events.
- Contract execution request by terra12z8vz3vgnalt8trykd6nntdyp54e95yqsdtjj3 to terra1xx5t5em3aza3lst0s5yc7rjgx9psapa3345v2vzfqkrprhw3vv6q3hahxy. Attached native funds requested: none (explicit empty list). Contract instructions and resulting effects are not decoded here.
Declared research links
Open the accounts, validators and proposals named in supported message fields. These links do not establish signatures, ownership or completed actions. First 20 top-level messages only; unsupported or missing references are omitted. Multi-send recipient links are shown with their declared output rows.
Show 2 declared references
Message 1 · Declared sender
terra12z8vz3vgnalt8trykd6nntdyp54e95yqsdtjj3Message 1 · Requested contract
terra1xx5t5em3aza3lst0s5yc7rjgx9psapa3345v2vzfqkrprhw3vv6q3hahxy
Transaction 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.
Transaction response provenance
- Public requested provider
- Withheld or unavailable
- Public response provider
- Withheld or unavailable
- Provider-reported response height
- 30866074
This evidence belongs to the original successful source read shown above. Cached or stale records retain that response's provider and height fields. A response height is separate from the transaction's inclusion block; it does not independently verify chain state or execution.
Only recognized public provider origins are displayed. Missing or withheld provider evidence does not make the transaction's fields independently verified.