Open a recent block and start asking questions. How many transactions are in it? What fees did it collect? When did it arrive? Which pool does the site say found it?
Suddenly the network stops being an abstract diagram. You have a real record to examine.
Begin with a single block
Open a block explorer such as mempool.space. A block explorer is a website that shows Bitcoin’s blocks and transactions. Look at a recent block. Find its height, timestamp (the time recorded in the block), number of transactions and fees. Then open the block before it and compare the two times. The gap does not have to be ten minutes.
One block gives you an example. Several blocks give you more context. Neither one proves a long-term trend.
A pool label needs context
A mining website may label a block with a pool’s name. That label does not tell you who owns each machine that worked on the block. And the portion of recent blocks a pool found does not directly measure how many machines mine with it.
Before you use a label to tell a story about the industry, check how the site assigns labels and what time window it uses. A percentage with many decimal places can still be a rough, noisy estimate.
Hashrate is inferred, not read from one giant meter
Nobody has a meter connected to every mining machine in the world. Instead, websites estimate the network’s total hashrate from two things: how fast blocks are being found and the current difficulty.
Short time windows react quickly but bounce around. Longer windows smooth out the noise but react more slowly to real changes. If two dashboards disagree, compare their time windows and methods before deciding one is wrong.
Bring it back to your shift
Keep three views in mind. The miner tells you how the machine itself is running. The pool tells you what work it received and how it counts and pays for that work. Network data tells you about blocks, difficulty and fees.
When those views disagree, you have a question to investigate. When they make sense together, you can explain what the machines are doing—and why it matters—with much more confidence.
You can start contributing in small ways. Ask a useful question. Help a colleague understand a confusing number. Write down an explanation that would have saved you an hour. You do not have to know everything before you have something to contribute.
Optional reading for this lesson
Continue your study
Reading for this lesson
Explore blocks and transactions.
Explore network data and indicators.