How to Use GNKScan: A Practical Gonka Explorer Guide
Find blocks, transactions, participants, epoch phase, GPU counts and GNK price on GNKScan — the public block explorer for the Gonka network.
GNKScan is the public window onto Gonka: a Cosmos-based chain where consensus power comes from proven AI compute rather than staked tokens. This guide is a map of the explorer itself — what each surface means, how search works, and how to read a healthy network versus a degraded one.
Start on the home page
The home page is a live network console, not a marketing page.
- GNK price — mid-market or tracked wrap price (see the market tile). A sparkline appears when price history is available.
- Latest block — last confirmed height from the indexer tip, with average block time when known.
- Transactions — cumulative indexed count and a short TPS sample from the recent feed.
- Epoch — current epoch index, phase (for example Inference), and progress through the PoC cycle.
- Inferences (est.) — when available, indexed inference-related transactions in this epoch's block range. The on-chain request counter has been unreliable; the estimate is honest about being index-derived.
- GPUs Live — GPUs in INFERENCE status among active-epoch participants only (not every address ever registered).
Below the console, twin feeds show latest blocks and transactions. Use them as a heartbeat: if heights stop advancing while the chain is live, check the status page.
Search: address, tx hash, or height
The search band accepts:
| Input | Opens |
|---|---|
Decimal height (4969993) | Block detail |
| 64-character hex hash | Transaction detail |
gonka1… bech32 address | Address page |
Invalid queries return to home with the search modal prefaced — they do not invent a page.
Blocks and transactions
- Blocks lists the tip with transaction counts. Empty blocks are real: Gonka still advances height without user activity.
- Open a height for hash, proposer (when the scanner indexed headers), gas totals, and the txs in that block.
- Transactions is a typed live feed. Message types include transfers, inference lifecycle messages, proof-of-compute batches, and reward claims. CSV export is available for offline analysis.
Participants, inference, and models
- Participants — the active set and compute-derived weights for the current epoch. This is not a bonded-token validator list; power is computational.
- Inference — who is serving AI work this epoch, with model lists and node counts. Drill into a participant for hardware detail when available.
- Models — models registered through governance, with units-of-compute parameters that price inference.
Epochs in one paragraph
Everything economic on Gonka settles on an epoch clock: proof generation, validation, a long inference-serving stretch, then settlement. Progress on the home tile is height-based. For the full lifecycle, read Gonka Epochs Explained.
Price and tokenomics
GNK is the native unit of account for inference fees and rewards. Tracked market price may come from the HEX order book or from Wrapped Gonka (WGNK) market data when the book is unreachable. For the economic design — escrow, vesting, zero gas — see Gonka Tokenomics.
When you see "—" or Degraded
GNKScan prefers a missing value over a fabricated one. Em-dashes mean a trusted upstream did not return that field. A Degraded chip means network stats or the scanner path failed; feeds may still work from cache. The status page lists which legs are healthy.
For builders and agents
- Public overview JSON:
/api/overview - Machine-readable site map for LLMs:
/llms.txt - Glossary of terms: /glossary
If you are comparing Gonka to other decentralized compute networks, start with Gonka vs Bittensor or Gonka vs Akash.