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 30696742

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-05T02:30:48.303Z
Transactions
2
Configured RPC observations
2
Block hash
9940B33B18049DDDBD4C2DE144778DFED12D468320095DFD75FA10B79F00E5D0
Parent hash
73A1A0DC9B1B94B4DF8D3737E0652CC0103FE7C40014748F5FE3C02CECE77709
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-05T02:31:45.824Z. Record read at 2026-11-08T11:58:40.437Z. 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
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-11-08T11:55:01.523Z (stale source observation). This is separate from the block-context observation at 2026-11-08T11:58:40.515Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-11-08T11:58:40.515Z. New bounded context. Returned block time: 2026-10-05T02:30:48.303392046Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
2
Failed transactions
0
Gas wanted (units)
5040753
Gas used (units)
4771269

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.

  • 145.730913 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
1E2A5CA856ED964FBC4B802E66A2B8CA46E422ABF3B703E4E94FD9FB10DF91BB7Success (code 0)66803756316818.922149 LUNC
2CCF56E3EDCE42763DAAE6D3B34D0286D869AD0BF2DC9B3B36C170DC689A5EC0ASuccess (code 0)43727164208101126.808764 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.