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

487036783256502FD7FEAC0BEE2C1D2D0BCC06A80B30D04A0BAA1DC485EB54DB

Reported execution
Success (code 0)
Block
30774822
Timestamp (UTC)
2026-10-10T10:57:00.000Z
Gas used / wanted
123640 / 141242

Declared fees

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

  • 4.096018 LUNC
Declared gas limit
141242
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.

AssetExact amountSender walletRecipient walletMovement evidenceMessage index
Luna Classic (LUNC) logoLUNC4.096018terra177dxlhrx…xqc0u3keg6terra17xpfvakm…8c5lkaeqfa
  • Curated reference: Fee Collector

    Module account · role evidence

Transaction fee0
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.

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.

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

      1. Contract execution request by terra177dxlhrxtxrtajwrt5xpsm7hqvc6xqc0u3keg6 to terra1rfe47us97720ghua5mqhr30zq4yp85jpxjw07ehqx87c856288qqtvjclq. 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

        terra177dxlhrxtxrtajwrt5xpsm7hqvc6xqc0u3keg6
      • Message 1 · Requested contract

        terra1rfe47us97720ghua5mqhr30zq4yp85jpxjw07ehqx87c856288qqtvjclq

      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-15T22:31:57.093Z. 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
      30854800

      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.

      Verify transaction in Finder

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