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 30773529

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-10T08:49:31.893Z
Transactions
2
Configured RPC observations
2
Block hash
5C9B1E20172F4E9DF3E2AC19CA831DE3651F3C1D543EB46535B9F25DCD8FD579
Parent hash
9FA4EA86576271C0DED54C3D5A4F65B5A81E7F485DA3918515C3F2DFAA50AB6E
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-10T08:50:01.928Z. Record read at 2026-10-14T10:38:34.284Z. 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
2
Validated transaction identities
2
Retained transaction records
2 / 100 limit
Proposer consensus address
097C671DCA2E57D767A0C10CAACD35B1BBF41EDE

Current validator key match

The returned current validator directory associates this consensus key with Battle-Force ⭐️CL8Y Node⭐️.

terravaloper1dj4hyxw2r0rmhf8frvxre4xmttfm9p9922psdg

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-10-14T10:37:59.677Z (stale source observation). This is separate from the block-context observation at 2026-10-14T10:38:34.302Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-10-14T10:38:34.302Z. New bounded context. Returned block time: 2026-10-10T08:49:31.893203724Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
2
Failed transactions
0
Gas wanted (units)
1066127
Gas used (units)
811095

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.

  • 30.463254 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
134947E5DDA1BE8E4BE08D6AE35A8263F24AE3B27194648DA843E16837C94A702Success (code 0)39286530344511.393085 LUNC
2CEA8D29515B8E9010C386FD33B0AAD9BF42D903AB466B4C41F0AA882861F2D2DSuccess (code 0)67326250765019.070169 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.