Gonka Network Explorer
Blocks, transactions, GPUs and inference activity on the Gonka network.
Waiting for dataEpoch—
Block—
GPUs—
Blocks, transactions, GPUs and inference activity on the Gonka network.
Short, plain-language definitions for Gonka terms you'll run into on GNKScan — each one links to the full write-up in our blog for more depth.
Active participants are doing work this epoch (dozens); registered participants are every address ever registered since genesis (thousands).
An epoch is Gonka's unit of time — a fixed span of blocks that cycles through proof-of-compute, validation, inference service, and settlement.
Every Gonka inference request is two on-chain messages — start inference escrows the max cost, finish inference settles the actual cost and refunds the rest.
The GPU worker in a Gonka participant's stack — it generates proof-of-compute batches and serves AI inference requests.
An AI model registered on chain through Gonka governance, each with its own units-of-compute-per-token pricing constant.
A participant's proven-compute score from the last completed proof-of-compute cycle — it drives consensus power, work allocation, and model assignment.
Gonka's consensus mechanism — participants prove GPU capacity by generating transformer-based proofs each epoch, and accepted proofs become voting power.
The base on-chain unit GNK amounts are stored in — like ucosmos or uatom, "u" marks a micro-denomination one millionth of a whole GNK.