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 30696278

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-05T01:45:00.794Z
Transactions
3
Configured RPC observations
2
Block hash
21AE2E28450628A188E752158FA264EDC913B9C33C3D12BFF259D14BAA18242A
Parent hash
006664D10E5898A1809BFFCE5A731D09F5A79826D9A883BC9B7A68219FFA3BD5
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:45:32.666Z. Record read at 2026-11-13T14:11:21.644Z. 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
E3789EC93AD0D00741238CAB3E44BAB1CB732682

Current validator key match

The returned current validator directory associates this consensus key with JESUSisLORD 2.

terravaloper10adzm06jk29w6cq0ytmg96xmfwpl4x6xun29uz

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

Source: Terra Classic RPC. Successful paired source read: 2026-11-13T14:11:21.822Z. New bounded context. Returned block time: 2026-10-05T01:45:00.794230229Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
3
Failed transactions
0
Gas wanted (units)
1553879
Gas used (units)
1200884

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.

  • 44.164962 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
1E62038020298BADD696085D988AEEFA0D4E62662C78DFFD8217FFEABE08B51E3Success (code 0)1412421236734.096018 LUNC
25CD250350DA2827F225E3EC9595F32C4064C88FEB74840B015C4BE7DDBC66FC0Success (code 0)109263787149430.948944 LUNC
39CCD890D8294C78815186056B53DA62319BDB8106E282FF6EE6129ED192D0471Success (code 0)3200002057179.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.