Terra Classic transaction
87036F28F358F2CF3DD0FE218E710118CF54AE9062825A3B51CBEDA804F63E31
- Reported execution
- Success (code 0)
- Block
- 30766758
- Timestamp (UTC)
- 2026-10-09T21:41:30.000Z
- Gas used / wanted
- 813370 / 1185713
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 33.585321 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. 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 | 33.585321 | terra1lntj7yf0…d5nm7skrms | 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.
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 terra1lntj7yf0mhvgflf6dlwuunye3fh7d5nm7skrms to terra19kurhxfuf93p7ppcrgtxpdztaezssy8af29pj7un3nvn4q8te67qtmwk2l. Contract instructions, attached funds and resulting effects are not decoded here.
- Contract execution request by terra1lntj7yf0mhvgflf6dlwuunye3fh7d5nm7skrms to terra1vxhnzlr44ajzq84xra07gtvyv5saxmsyz6cd5cewqm479znvsepqzdkk05. Contract instructions, attached funds and resulting effects are not decoded here.
- Contract execution request by terra1lntj7yf0mhvgflf6dlwuunye3fh7d5nm7skrms to terra14khv3qkz47xxv8z2lla70lfj257phzkn5p0vs99c8n53qa5ggypqcdn2vz. Contract instructions, attached funds and resulting effects are not decoded here.
Memo
Rottweiler add liquidity
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