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

3F94701AC21740E62292434596C5E19CDC6A7B47F87AA033B8DAAAE3DF454862

Reported execution
Failed (code 5)
Block
30765784
Timestamp (UTC)
2026-10-09T20:05:26.000Z
Gas used / wanted
251999 / 1629654

Reported execution failure

These are source-reported diagnostic fields. They do not establish fee collection, account balances, a refund or the outcome of a later retry.

Response code
5
Reported codespace
sdk
Show reported failure log

The log is untrusted source text and may include sender-supplied content. Links and instructions in it are not endorsed.

failed to execute message; message index: 0: spendable balance 1046399080628uluna is smaller than 1046422580578uluna: insufficient funds

Declared fees

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

  • 46.15995 LUNC
Declared gas limit
1629654
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: Unavailable. 0 supported native legs retained; total supported count unverified. At most 100 legs are retained.

Execution failed; completed native movements are not decoded. Transaction execution failed. Successful native movement decoding is withheld; fee collection is not reconstructed.

No supported native movement rows are displayed.

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.

Execution failed. Contract event interpretation is withheld.

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.

Execution failed. Contract event interpretation is withheld.

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. /cosmos.bank.v1beta1.MsgSend

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.

Execution failed. Do not treat these requested actions as completed.

  1. Send request: 1062357.949825 LUNC from terra16z2w2qe5y80hz4vpyv6gjwq2gmrrmakgy6p667 to terra18a5ctlzjn97mc7r590a83aps33mg0mvm4up8c3.

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

    terra16z2w2qe5y80hz4vpyv6gjwq2gmrrmakgy6p667
  • Message 1 · Requested recipient

    terra18a5ctlzjn97mc7r590a83aps33mg0mvm4up8c3

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-16T02:29:16.518Z. 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
30857195

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.