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 30862663

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-16T11:30:00.819Z
Transactions
3
Configured RPC observations
2
Block hash
B284C5516DEAB26E580A82B16CAFBE2DA97813F4191A60153EF648BCCE24E44E
Parent hash
DE61DD5B069FF6C5E8A16556188B9F9AF4AA009B6C9C55D88C3E50E3353A81BC
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-16T11:30:44.639Z. Record read at 2026-10-26T16:01:07.389Z. 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
FDAAC8D57C253F86CEDDC9F2BC8BF771EC961730

Current validator key match

The returned current validator directory associates this consensus key with TCB @THORmaximalist.

terravaloper1mpmn2y9qw4dn6z2q3a7hy4c3wjztmvu7wz4r4u

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-26T16:00:34.448Z (live source observation). This is separate from the block-context observation at 2026-10-26T16:01:07.596Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-10-26T16:01:07.596Z. New bounded context. Returned block time: 2026-10-16T11:30:00.819145439Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
3
Failed transactions
0
Gas wanted (units)
877428
Gas used (units)
482472

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.

  • 16.585412 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
119A0D1FAA81AB3FB53B63B1A1B1178B9DD4FE4497F1BDA1F2F16411D9B0D7A64Success (code 0)300000111067Empty fee coin list
23771936BC20E4AE4B7C541190AF987FF3B6F606CF7C0FA3180E1B0BEDC77DC7ESuccess (code 0)2574281656457.465412 LUNC
3574BF077461C13414DB39281743BCDF395178C8C91A44D75111FA12ABB3D4F69Success (code 0)3200002057609.12 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.