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 30576912

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-09-26T21:23:26.027Z
Transactions
2
Configured RPC observations
2
Block hash
B5A7EAE87FB7218D7EAE0F68D678B80ACE55F229ABE118997BD2441A9AEC2A01
Parent hash
81D5F8F028360CE434A9EE9CAB7D37242B3BE184C327DB334A357B21BAE7E430
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-09-27T00:31:19.264Z. Record read at 2026-11-03T14:13:20.667Z. 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
77C085B65C3E76D7202F87B1D55BD6164D7DC5A4

Current validator key match

The returned current validator directory associates this consensus key with Stakely.io.

terravaloper108lmrztvc3pc3w774shgvpry4d3lf79k2ummna

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

Source: Terra Classic RPC. Successful paired source read: 2026-11-03T14:13:20.805Z. New bounded context. Returned block time: 2026-09-26T21:23:26.027164628Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
2
Failed transactions
0
Gas wanted (units)
1320406
Gas used (units)
1170978

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.

  • 40.610986 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
10BA8EB2C2F4073366EC8F5F286D5B1D0ADB2B405F645D549D7179299C9D893F8Success (code 0)92768586761229.222077 LUNC
2A4CF0ABBFC77C2D6422CEC077672B0B1153FF7EDE0C3D127FF9E01E44B088C47Success (code 0)39272130336611.388909 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.