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

Chain history and coverage · Search

Terra Classic block 30918494

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-20T07:32:11.050Z
Transactions
3
Configured RPC observations
2
Block hash
F6FE08D120AF17FC3DA6502C288A3C03BC9552995FB8593D58825E473654E794
Parent hash
632300BA00E4A61D43BDD44096A41798F2E84C9C0F33BADAB99BB446E1E3D6CA
Evidence, timestamps and limitations

Source: StatsBin's canonical index of configured public Terra Classic RPC block/results observations. Endpoint agreement is not independent consensus verification. The transaction count includes successful and failed transactions.

Indexed at 2026-10-20T07:33:04.099Z. Record read at 2026-11-16T13:21:33.812Z. These are separate from the block time.

Coverage here is this one stored block. It does not establish complete earlier history or retained raw RPC bodies. The separate bounded context below may supply a matched proposer and transaction execution/gas records. Declared token fee amounts are shown where transaction bytes support them. Collected payments and decoded transaction effects remain unavailable here.

Reading this block's bounded proposer and transaction context…

Inspect preceding height (coverage may differ)

Network activity and interval comparisons · Burn evidence explorer

Block proposer and transaction results

Observed block context. The returned transaction and execution-result vectors match the stored block and have supported codes and gas values.

Inspect the consensus proposer, ordered transaction results and exact gas units for this stored block. Context supports blocks of at most 100 transactions.

Returned transactions
3
Validated transaction identities
3
Retained transaction records
3 / 100 limit
Proposer consensus address
F33F198ECE766D0352659C66B905A16535EB403D

Current validator key match

The returned current validator directory associates this consensus key with LuncGoblins | #blamefrag.

terravaloper1uml7n30kyndkmjvrgy6d63kffpn6hvztx3fxr6

This current key association does not prove who operated the proposer at this block's historical time. Names are validator-provided labels.

Validator directory observation: 2026-11-16T13:15:58.523Z (stale source observation). This is separate from the block-context observation at 2026-11-16T13:21:33.973Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-11-16T13:21:33.973Z. New bounded context. Returned block time: 2026-10-20T07:32:11.050060574Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
2
Failed transactions
1
Gas wanted (units)
20535864
Gas used (units)
20428428

Declared transaction fees

Fee amounts declared in the returned transaction bytes, including transactions with failed or unknown execution results. These are not proof of collected payments, taxes, refunds or burns.

  • 715.540056 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
1C97A693981BE1904520B33077A2E0B445C6600109F7FD3034185F16FFF092168Success (code 0)1412421236734.096018 LUNC
21D432E0F4D35EBD1795E5869B0B930D6B91A71671F1B00D82F113D4AA0F11801Failed (code 11)2000000020000000700 LUNC
39987FC96B5CA8D1E70938722994E7EEF8E472B7AA68D6588C7BC6AA636609BACSuccess (code 0)39462230475511.444038 LUNC
Display page 1 / 1; up to 25 retained records per page.

Gas includes supported failed transactions and is not a token fee. The consensus address does not establish a validator operator or historical owner. One matched block/results pair does not establish independent provider agreement, complete chain history, decoded transaction effects or burn attribution.