Understand the ClearCoin network
Learn how to find on-chain records, interpret explorer data, and integrate with the public API.
Search the chain
Find blocks and transactions by height or hash.
Read guide →Read block data
Understand block fields, status, and execution totals.
Read guide →Read transactions
Interpret status, gas, events, and execution codes.
Read guide →Build with the API
Use the indexed data in your own application.
Read guide →Finding records
The global search accepts the following exact record identifiers.
Block height
844,116
Commas are optional
Block hash
64 characters
Full hash required
Transaction hash
64 characters
Full hash required
Address
clearcoin1…
Validator or consensus
Understanding block data
A block page combines canonical header data with aggregate execution results.
- Height
- Sequential position of the block in the canonical chain.
- Timestamp
- UTC time reported in the block header.
- Block hash
- Canonical CometBFT block identifier.
- Proposer
- Validator address that proposed the block.
- Transactions
- Number of normalized transactions included in the block.
- Finalized
- The block is persisted as part of Explorer's canonical indexed chain.
- Gas utilization
- Total gas used divided by total gas wanted for indexed transactions.
Understanding transaction data
Transaction pages summarize execution without exposing encoded transaction bytes.
Successful transaction
A zero execution code indicates the network accepted and executed the transaction successfully.
Failed transaction
A non-zero code indicates execution failed. The code, codespace, and bounded log can help identify why.
- Transaction index
- The transaction's zero-based position within its block.
- Gas wanted
- Maximum execution units requested by the transaction.
- Gas used
- Execution units actually consumed.
- Events
- Public event types emitted during execution; attribute values are not exposed.
- Memo and fees
- Shown only when safely decoded and indexed; unavailable fields are clearly labeled.
Data freshness
Explorer presents independently indexed data and may briefly trail the network tip.
15-second refresh
Dashboard data is cached and refreshed every 15 seconds. Manual refresh is also available on the home page.
Indexer status
Synchronized means the indexer is current. Catching up means valid data is available while newer blocks are still being processed.
Public API
Read the same bounded, indexed records used by the Explorer interface.
Explorer glossary
Core terms used throughout the interface.
- Block
- A finalized group of transactions and consensus metadata added to the canonical chain.
- Block height
- The sequential number identifying a block's position in the chain.
- Block hash
- A unique 64-character cryptographic identifier for a canonical block.
- Proposer
- The validator address responsible for proposing a block.
- Transaction hash
- A unique 64-character identifier derived from the submitted transaction bytes.
- Gas wanted
- The maximum execution units requested for a transaction.
- Gas used
- The execution units actually consumed while processing a transaction.
- Indexer
- The service that reads network data, normalizes it, and persists it for Explorer.
Common questions
Quick answers about Explorer behavior and data scope.
Can I send transactions from Explorer?+
No. Explorer is read-only and never requests wallet keys or signatures.
Why can’t I find a recent transaction?+
The indexer may still be catching up. Wait for the next refresh and confirm you entered the complete 64-character hash.
Why is a fee or memo unavailable?+
Explorer only displays fields that have been safely decoded and indexed. It does not expose unreviewed raw payloads.
Does Explorer show pending transactions?+
No. It displays transactions contained in canonical indexed blocks, not a mempool view.