YSKAR

Right now

Block height
Network hashratework of the last 24 blocks, divided by their time
Difficultyrecomputed for every block
Block time, last 50 blockstarget: 600 s
Transfers waitingat the main node
Active minersreported, not verifiable
Mining sessionsreported, not verifiable
Nodes reportingreported, not verifiable

History, read from the blocks

Every block of the chain, summed by day in UTC. The history is complete up to block ; the figures above are read live.

Period

Hashrate per day

Show the values as a table

Blocks per day

Complete days only. At the target block time a day has 144 blocks.

Show the values as a table

Blocks per day, by finder

Complete days only. Pool blocks carry the pool's name in the chain; a block that pays a single address counts as solo.

Show the values as a table

Average block time per day

Seconds between blocks, averaged over the day.

Show the values as a table

Who finds the blocks

In the first weeks every block was found solo. Today nearly all blocks come from two pools, and most of them from one.

This matters. A pool's operator chooses the transactions and the parent of every block the pool works on, and whoever directs most of the hash power can build the chain with the most work. More pools and more solo miners make the chain harder to steer.

The pools, and how to run your own
Share of blocks found

Counted from the chain. The first bar follows the live chain, the other two end where the embedded history ends.

The latest blocks

Select a block to see its header, recompute its proof of work and read its transactions.

Open the explorer
Newest first
HeightFoundByPaid toDifficulty

Where the numbers come from

Not every figure on this page has the same weight.

From the chain
Height, difficulty, supply and every chart on this page. The hashrate is the work in the latest blocks divided by the time they took. Anyone who runs a full node can recompute all of it.
Reported
Active miners, sessions, nodes and the hashrate a pool states about itself. These are self-reports. They show a direction, and nobody can check them.
The mirror
This page and the explorer read a database copy of the chain, so that they load quickly. The mirror checks every block it stores, but it is a convenience. The chain is what the full nodes agree on.
Seed nodes
A new node first contacts pool.yskar.app:8646 or yskar-seed2.dynv6.net:8646. Both are run by the same operator. After that, nodes exchange the addresses of other nodes among themselves.
The same fjord at first light: a pale sky over snow-covered mountains and still water.

It's still early here.

Day . The first light is only just coming up over this network. The people who shape it are the ones who are here now.