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

8C6EB79303A1B6E81B04716DF704A155B486F0CB8E66CA743027F30FE0E97D80

Reported execution
Success (code 0)
Block
30775030
Timestamp (UTC)
2026-10-10T11:17:34.000Z
Gas used / wanted
141136 / 400000

Declared fees

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

  • 16 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.

AssetExact amountSender walletRecipient walletMovement evidenceMessage index
Luna Classic (LUNC) logoLUNC16terra1zafpjz7h…2taxtl8jeuterra17xpfvakm…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.

Message types (1)

Declared messages describe attempted actions. Completed native transfer events are interpreted separately 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. Only the supported native movement table above interprets resulting transfer events.

  1. Contract execution request by terra1zafpjz7h4x9cd8n5rf9lxz7tru352taxtl8jeu to terra15p8su45k45axng8ue59rl6zph4at27s49u3agr6uqrx3dhcxpg3qt0ekdt. Contract instructions, attached funds and resulting effects are not decoded here.

Memo

{"do_redemption":{"v":1,"asset":"DO","to":"do1zh4a84f475z7gw22l32a78lvrh6u97lztv5jk8"}}

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-10T21:41:25.518Z. 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.