Terra Classic transaction
F9DF2A59135C6E1ACD8097EABB3C2FE387D0B4F0399C311AA38DFF40D474A439
- Reported execution
- Success (code 0)
- Block
- 30773498
- Timestamp (UTC)
- 2026-10-10T08:46:28.000Z
- Gas used / wanted
- 110862 / 134661
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 3.814273 LUNC
- Declared gas limit
- 134661
- 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. 2 supported native legs retained of 2 parsed. At most 100 legs are retained.
| Asset | Exact amount | Sender wallet | Recipient wallet | Movement evidence | Message index |
|---|---|---|---|---|---|
 LUNC | 3.814273 | terra1rn2j06hj…nyy6e9fxvk | terra17xpfvakm…8c5lkaeqfa
| Transaction fee | 0 |
 USTC | 22.135339 | terra1rn2j06hj…nyy6e9fxvk | terra1kq2rzz6f…mk68wplle5 | 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.
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.
0 supported events in the selected message logs.
No supported CW20-style transfer events were present in the selected event representation.
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.
- /ibc.applications.transfer.v1.MsgTransfer
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.
- IBC transfer request: 22.135339 USTC from terra1rn2j06hjvdadw2njxccvhptsz87fnyy6e9fxvk through transfer/channel-1. Receiver field: osmo10a3k4hvk37cc4hnxctw4p95fhscd2z6h2rmx0aukc6rm8u9qqx9smfsh7u (destination address not verified here). Declared timeout height: Revision 1, height 72256329. Declared timeout timestamp: No timestamp timeout declared (0). Packet memo present; its instructions and downstream actions are not interpreted. These fields do not establish the destination chain, packet acknowledgement, delivery, timeout execution, refund, swap or recipient ownership.
IBC transfer packet-send events
Local send events are interpreted only when successful execution is established. A reported destination channel does not identify or verify the destination chain or packet delivery.
Event source: Structured logs. 1 send event returned in the selected representation. 1 supported packet identity interpreted.
Packet sequence 394817
- Source endpoint
- transfer/channel-1
- Reported destination endpoint
- transfer/channel-72
- Reported connection
- connection-11
- Channel ordering
- Unordered
- Reported timeout height
- Revision 1, height 72256329
- Reported timeout timestamp
- No timestamp timeout recorded (0)
- Message index (source)
- 0
Packet interpretation and limits
Only standard transfer-port send events with supported identifiers are interpreted. One event representation is selected; logs and transaction events are never merged. Source message indexes are retained without inferring a match to a declared top-level request. Packet data and memo instructions are not decoded. These observations do not establish acknowledgement, receipt, timeout execution, refund, swap, receiver ownership or cross-chain completion. Timeout values are reported fields, not an expiry decision.
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 1 declared reference
Message 1 · Declared source sender
terra1rn2j06hjvdadw2njxccvhptsz87fnyy6e9fxvk
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
- 30863564
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.