Bitcoin network dashboard

Read the chain tip, backlog, fees, issuance and proof-of-work together. Each figure states whether it is observed, estimated or fixed by protocol rules.

Current Bitcoin network state

Loading the latest cached network observation…

Block height—

Mempool transactions—

Fast fee estimate—

Issued supply—

Current fee targets

Fee estimates are local observations and can change between blocks. A node’s mempool can differ from another node’s view.

One chain, several layers of evidence

The chain tip and block subsidy are protocol facts once a block is accepted. The mempool is local: nodes may hear transactions in a different order or reject different low-fee transactions. Hashrate is estimated from block timing and difficulty, not measured from every mining machine.

Read freshness before precision

The dashboard keeps a last-good observation and shows when it was recorded. During a source outage, an older labelled value is more useful than a blank card—but it should not be mistaken for a new block.

Explore how Bitcoin works or inspect issuance in the supply and halving explorer.

Network signals at a glance

Signal	What it describes	What it does not prove
Block height	Accepted blocks since genesis	Wall-clock speed
Mempool vsize	Queued transaction data seen by a node	A global queue
Fee estimate	Modelled bid for a target	Guaranteed confirmation
Difficulty	Proof-of-work target adjustment	Miner profitability
Issued supply	Maximum subsidy claimable by height	Coins available for sale

How Bitcoin.now handles tool data

Calculated values

Deterministic tools state their assumptions beside the result. They do not present a model as an executable quote.

Observed values

External observations use read-only public data, retain the latest valid cache, and show freshness when a source is delayed.

Safety boundary

No tool trades, broadcasts, connects a wallet, stores a secret, or gives personal financial advice.

Review the data methodology, editorial policy, and risk disclaimer.

Using bitcoin network dashboard responsibly

Is the mempool global?

No. Each node maintains its own valid unconfirmed transaction set. Well-connected nodes often look similar, but policies, timing and evictions can produce differences.

Why is hashrate estimated?

Mining machines do not report to one registry. Dashboards infer work from difficulty and the random pace of discovered blocks, so shorter windows are noisy.

What happens during a source outage?

Bitcoin.now retains the latest valid observation and labels its age. Protocol calculations still work, while values that need a new observation are not presented as fresh.

Read the network vital signs together

Block height, difficulty, estimated hashrate, mempool size and fee estimates each describe a different part of the system. Reading them side by side shows whether the network is calm, congested or in the middle of a difficulty change.

Height and difficulty are exact; hashrate is inferred

Height is a count of blocks. Difficulty is a number in the consensus rules. Hashrate is estimated from how fast recent blocks arrived against that difficulty, so it moves with luck over short windows.

Difficulty changes only every 2,016 blocks.
A hashrate estimate over one day can swing 10–20 % on variance alone.
Compare seven-day averages, not single readings.

How difficulty adjustment works →

The mempool is a queue, not a fact

Each node keeps its own list of unconfirmed transactions. Count and total virtual size describe the node the dashboard read; they rise before fee rates do and fall as blocks clear them.

A large backlog with low fees usually means low-priority consolidation.
Fee estimates are what recent blocks cleared at, not guarantees.
The next-block estimate matters most when a payment is urgent.

Open the mempool explorer →

Dashboard fields and their meaning

Field	What it measures	Refresh	Use it to
Block height	Blocks in the longest valid chain	Every block, ~10 min	Find the next halving or difficulty change
Difficulty	Work required per block	Every 2,016 blocks	Judge mining competitiveness over months
Hashrate (est.)	Work rate implied by block timing	Continuous estimate	Spot large shifts in mining activity
Mempool vsize	Unconfirmed data waiting	Minutes	Anticipate fee pressure