Skip to main content
Terra Classic statsLUNC · USTC · ON-CHAIN DATA
StatsBin logo

StatsBin.

Terra Classic Stats

Burn AdsSearchWallet
HomeNetworkBridgesSupplyStakingBurnsValidatorsWalletsProposalsNewsGamesTools

StatsBin.

The Terra Classic observatory

Independent LUNC and USTC data, from supply and burns to validators, wallets and governance.

Explore

LUNC dashboardIndexed chain historyLUNC stakingLUNC supplyBurn intelligenceValidatorsGovernanceLUNC newsLUNC Games

Connect

Data methodologyMachine access · LUNCAgentStatsBin LUNC Validator Follow on X Contact
© 2026 StatsBin · Independent Terra Classic intelligence
PrivacyTermsCookiesAccessibility
Transaction counts and fees

Terra Classic transaction

5C2EACAF8DCAC09715841D9847B1E2C4A7ED2485881DD22EB116275269E146BA

Reported execution
Success (code 0)
Block
30774959
Timestamp (UTC)
2026-10-10T11:10:34.000Z
Gas used / wanted
115274 / 140345

Declared fees

Transaction fee fields, not a reconstruction of fee collection or payer balances.

  • 3.975273 LUNC
Declared gas limit
140345
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.

AssetExact amountSender walletRecipient walletMovement evidenceMessage index
Luna Classic (LUNC) logoLUNC3.975273terra1ea9svw5h…wwwajcnwchterra17xpfvakm…8c5lkaeqfa
  • Curated reference: Fee Collector

    Module account · role evidence

Transaction fee0
Luna Classic (LUNC) logoLUNC100,000terra1ea9svw5h…wwwajcnwchterra1kq2rzz6f…mk68wplle5Transfer event0
Page 1 / 1; up to 30 legs per page.
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.

  1. /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.

  1. IBC transfer request: 100000 LUNC from terra1ea9svw5h8uhzynxjafeu4ka3xe34wwwajcnwch through transfer/channel-1. Receiver field: osmo10a3k4hvk37cc4hnxctw4p95fhscd2z6h2rmx0aukc6rm8u9qqx9smfsh7u (destination address not verified here). Declared timeout height: Revision 1, height 72262793. 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.

  1. Packet sequence 394830

    Source endpoint
    transfer/channel-1
    Reported destination endpoint
    transfer/channel-72
    Reported connection
    connection-11
    Channel ordering
    Unordered
    Reported timeout height
    Revision 1, height 72262793
    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

    terra1ea9svw5h8uhzynxjafeu4ka3xe34wwwajcnwch

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 2026-10-13T22:14:27.362Z. This is a source observation, not independent consensus verification. Linked block coverage may be incomplete.

Verify transaction in Finder

Inspect the reported execution result, fees, gas and message types on Terra Classic.