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 30918532

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-20T07:35:56.226Z
Transactions
3
Configured RPC observations
2
Block hash
73B1EC70EEF15D7A5A5B46221C79DDC3118C34F5050227BD501F6AE6A6B683FE
Parent hash
8F117D0F23521C36F7EE3408F87AE70AC21D7AF260CB343A45C0DE437D6AA868
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:36:47.105Z. Record read at 2026-11-16T08:20:57.602Z. 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
8C17AD9E9B5EC1DCA0781D4B1FD725088B268957

Current validator key match

The returned current validator directory associates this consensus key with Interstake One.

terravaloper1ya23p5cxtxwcfdrq4dmd2h0p5nc0vcl96yhjra

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-16T08:20:45.539Z (live source observation). This is separate from the block-context observation at 2026-11-16T08:20:57.748Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-11-16T08:20:57.748Z. New bounded context. Returned block time: 2026-10-20T07:35:56.226145417Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
2
Failed transactions
1
Gas wanted (units)
9438417
Gas used (units)
4437577

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.

  • 267.4385 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
11EF6B4159C8C8FDE2A8A2ED7E8919B209241148D3D0EFD16EB79329332454302Success (code 0)46217754025727130.911777 LUNC
26BAC630691E89FD66F45CEC9B31ED53B52A33C18C57B33909E67159BDE583DE5Failed (code 5)4675400288156132.430705 LUNC
3F7C086E4D43933C4EF99956CDA8B01D6202EAF064BBAA0661D96E14528D32DACSuccess (code 0)1412421236944.096018 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.