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 31012625

Chain
Terra Classic · columbus-5
Block time (UTC)
2026-10-26T20:12:25.938Z
Transactions
3
Configured RPC observations
2
Block hash
C7B4EF51D43B90872092C2CE24D3851CAFACECCA2EE686709E6E05367FEE3C36
Parent hash
1DA90450D6A60E5E9437960D388408B7B840C30851855A4B3A4D2997C3E49DD0
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-26T20:13:14.208Z. Record read at 2026-11-11T21:38:46.535Z. 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
7927208E439048B8F12F9315FE1654E2B5850DBA

Current validator key match

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

terravaloper1l3zgwrqxp55z8r39vp94v9emxwql5fpa6p9z6h

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-11T21:37:57.519Z (stale source observation). This is separate from the block-context observation at 2026-11-11T21:38:46.619Z. A missing match does not establish that the proposer is absent from the chain.

Source: Terra Classic RPC. Successful paired source read: 2026-11-11T21:38:46.619Z. New bounded context. Returned block time: 2026-10-26T20:12:25.938053536Z. Block identity is matched to the stored record at millisecond time precision.

Successful transactions
3
Failed transactions
0
Gas wanted (units)
1565182
Gas used (units)
975124

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.

  • 30.737781 LUNC
PositionTransactionExecution resultGas wanted (units)Gas used (units)Declared fee amounts
1184D585538C387F74EC65491F0DC1AD26A28C3013AF4CFC3BDA0D3182E7A71D3Success (code 0)240000113507Empty fee coin list
209201F9A9CA91A435DBEFA0E7BF0C90A4750EF0A7D9EC2197510D4E0062C137ESuccess (code 0)240000112715Empty fee coin list
3D874BB4A75AEFC1FA43237F1A14B62D848B04184309E3765707DC5AF1FF014AESuccess (code 0)108518274890230.737781 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.