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 30769052

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-10T01:27:47.264Z
Transactions
3
Configured RPC observations
2
Block hash
303CC64DCE92A5DFA9ACBA1BE23C06EAF4550EE8642DFE4C6248B034C3289F0B
Parent hash
2ADEA0347732D94C701CAE7AC7900FCA740F38CBA1EB9CA1B63ADF6DB488D87D
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-10T01:28:25.898Z. Record read at 2026-10-24T14:25:58.847Z. 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-24T14:25:02.101Z (stale source observation). This is separate from the block-context observation at 2026-10-24T14:25:58.943Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-10-24T14:25:58.943Z. New bounded context. Returned block time: 2026-10-10T01:27:47.264144026Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
3
Failed transactions
0
Gas wanted (units)
4780967
Gas used (units)
3014621

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.

  • 116 LUNC
  • 0.594593 USTC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
171BD873C3992343658F241961AEC490D47BF7D5FDB6F75EB787D0861162BD082Success (code 0)3809672628300.285726 USTC
2B6D86030D6B3CF08E78C72AB0A9BAC9596184F843630F23D691614748494490ESuccess (code 0)40000002491703116 LUNC
3CF772615A667D72D30DFD8F87B80A8B0392E1B8F37F539374AF36C2D5EBAF1C1Success (code 0)4000002600880.308867 USTC
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.