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 30919684

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-20T09:29:59.254Z
Transactions
3
Configured RPC observations
2
Block hash
35BC875AC1EFFE3A05BA37F6D22F66B0723383DD4E43CDDEECFBEFCDF032D5F8
Parent hash
46725D3788EE6F36425D69C58342895BE32FA997495E14251AD2A4046D76967D
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-20T09:30:56.333Z. Record read at 2026-10-26T14:27:07.620Z. 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
261986A0D28242408C0964B2AB6F1EA98FE39A19

Current validator key match

The returned current validator directory associates this consensus key with NITAWA.

terravaloper193zuma3tk69kvffz9nqnca7z99tz7ej5ze9s7k

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-26T14:26:25.669Z (stale source observation). This is separate from the block-context observation at 2026-10-26T14:27:07.672Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-10-26T14:27:07.672Z. New bounded context. Returned block time: 2026-10-20T09:29:59.254469237Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
3
Failed transactions
0
Gas wanted (units)
2300734
Gas used (units)
1842239

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.

  • 65.398078 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
1DE13E27A150FE76A8115D04DD11B410C3A2A04866F3E39C47534097FD55E9D8FSuccess (code 0)3200002057059.12 LUNC
20D07F884936994CB0E1C2E9BE39D8B68495E83DE94915A19C1B050EBDC494C53Success (code 0)2574281656967.465412 LUNC
38F5562828D0E0FE7FB73F80F242FA15CB3FB2102A1C38ED96B8199B001FCCD20Success (code 0)1723306147083848.812666 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.