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 30696394

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-05T01:56:32.581Z
Transactions
3
Configured RPC observations
2
Block hash
A386E768404709BD68D4CCABA650F84F6287643CDEC29F8138C4C07B0A67DA1A
Parent hash
049A895E476BA1C14E269E6BE165BB3A601BB9AD5044E0672C22CCE3710E4538
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-05T01:57:10.190Z. Record read at 2026-11-10T15:27:20.321Z. 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
40EEF85CDD9BCBABCB342B71FBFDB28DA3D79EF5

Current validator key match

The returned current validator directory associates this consensus key with 🌕 LunaClassicNode.com.

terravaloper1avlerps4ue6zjw59ul4ptgqqem0v3pxqje0k3m

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-10T15:27:14.150Z (live source observation). This is separate from the block-context observation at 2026-11-10T15:27:20.463Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-11-10T15:27:20.463Z. New bounded context. Returned block time: 2026-10-05T01:56:32.58137679Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
3
Failed transactions
0
Gas wanted (units)
1597866
Gas used (units)
1127521

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.

  • 45.948715 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
101BCE0A8DCB3380AE694000A31A5DB29F6A70CC72265E002A383A877A5189368Success (code 0)39277630338111.390504 LUNC
2211635469B749CE30998FA88D2F1E1E4F744D6D200D72481DC099ED0CBB6E0B0Success (code 0)57692250358916.341339 LUNC
3ED4B06A8DA8354C03E260BA0A1D795A5403DA9747C9A0A0A84356986AD98542CSuccess (code 0)62816832055118.216872 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.