Terra Classic transaction
9031E862D06C2FC3E7DEE9848B06E1F560EA6B8E60EA53FCD9741E7AA2E62046
- Reported execution
- Success (code 0)
- Block
- 30772606
- Timestamp (UTC)
- 2026-10-10T07:18:31.000Z
- Gas used / wanted
- 115438 / 138911
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 3.934655 LUNC
- Declared gas limit
- 138911
- 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 | 3.934655 | terra1gygragtv…939qer9ur5 | 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 (1)
Declared messages describe attempted actions. Completed native transfer events are interpreted separately 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. Only the supported native movement table above interprets resulting transfer events.
- IBC transfer request: 5281085 base units (ibc/E1E3674A0E4E1EF9C69646F9AF8D9497173821826074622D831BAB73CCB99A2D; decimals unverified) from terra1gygragtv7rhv86scnq4lkw0kw499939qer9ur5 through transfer/channel-19. Receiver field: axelar1j26g4rrz3tlrfnmlzpgr42qlsd78r942w26jln (destination address not verified here). Declared timeout height: No height timeout declared (0-0). Declared timeout timestamp: 2026-10-10T07:23:26.494604500Z (1791617006494604500 Unix nanoseconds). Explicit empty packet memo. 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 110917
- Source endpoint
- transfer/channel-19
- Reported destination endpoint
- transfer/channel-0
- Reported connection
- connection-31
- Channel ordering
- Unordered
- Reported timeout height
- No height timeout recorded (0-0)
- Reported timeout timestamp
- 2026-10-10T07:23:26.494604500Z (1791617006494604500 Unix nanoseconds)
- 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
terra1gygragtv7rhv86scnq4lkw0kw499939qer9ur5
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
- 30839814
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.