Audit One Day of Bitcoin Mining by Counting Its Blocks

To know how many new bitcoins were mined on a particular day, count the blocks in that day and the new subsidy included in each one. The often-quoted figure of about 450 BTC is a target-rate estimate based on 144 blocks and a 3.125-BTC subsidy. It is not a ledger entry stamped at midnight. A real calendar day might contain 143 blocks, 151 blocks, or another number. This guide shows how to define and check a day's result without confusing it with transaction fees or deposits into miners' wallets.

Choose a day before choosing a number

Specify the date and time zone first. One report might use midnight-to-midnight UTC; another might use New York local time. A block discovered near a day boundary can fall into different reports without either one inventing a block. For a reproducible answer, use a named range such as September 14, 2026, 00:00 through September 15, 00:00 UTC, with the end excluded. State the source of the block times and how boundaries were applied.

Blocks have heights that place them in chain order and timestamps recorded in headers. An explorer can show the heights and times of blocks inside a chosen reporting window. Count the entries on the accepted chain, not a screenshot of a miner's payout dashboard. A mining pool may send payments on a later date or wait for a balance threshold; that deposit calendar is not the network's block calendar.

Bit.Fan’s introductory guide to bitcoin mined per day emphasizes that new coins appear per block and that daily output varies. A careful audit adds two labels to that idea: the precise reporting window and whether the result uses allowed subsidy or actual coinbase creation. Without those labels, two “daily bitcoin mined” figures can differ for valid reasons.

Use the active subsidy at each height

The Bitcoin.org halving page identifies 3.125 BTC as the subsidy after the April 2024 halving at height 840,000. It also says the next reduction is due at height 1,050,000. For an ordinary day between those heights, multiply the accepted block count by 3.125 to estimate the maximum newly allowed subsidy. For a day crossing a halving, apply the older rate to blocks before the boundary and the new rate to blocks from the boundary onward.

Imagine, purely as an example, 143 accepted blocks in one UTC day entirely within the current subsidy era. At the full permitted amount, 143 times 3.125 equals 446.875 BTC. That differs from 450 by 3.125 BTC because the day has one fewer block than the 144-block shorthand. It does not mean anyone changed the monetary policy. The hypothetical block count should never be presented as an observed count for a real date.

Keep units straight. One bitcoin is 100 million satoshis, so 3.125 BTC is 312,500,000 satoshis. The Bitcoin developer reference for getblockstats describes its per-block “subsidy” and “totalfee” fields in satoshis. A sum of 143 full current-era subsidies is 44,687,500,000 satoshis, which is 446.875 BTC after dividing by 100 million. Mixing satoshis and BTC can make a result wrong by eight orders of magnitude.

Subsidy and coinbase payment are not synonyms

Bitcoin Core's reported “subsidy” field is the amount scheduled by protocol for that block height. A miner can generally claim up to that amount plus transaction fees in the coinbase transaction. Fees are existing coins paid by users, so they are not newly issued BTC. If an explorer displays a combined block reward, subtract the fees before using it as a creation figure. Counting combined coinbase outputs without that separation overstates new supply.

There is also a narrow exception: a miner may claim less than the full allowed subsidy. Multiplying block count by the scheduled rate gives a rule-based upper estimate for the period, while the exact newly claimed amount requires examining the coinbase payment and the fees of each block. A basic explorer may not expose every component clearly. State the method rather than claiming an exact observed issuance total from the target-rate formula.

Do not treat every block visible at first as final forever. Occasionally competing blocks appear at similar times and the network continues on one branch. A short-lived block that is not part of the eventual accepted chain should not be counted as an additional issuance in a settled historical audit. Waiting for further confirmations and using a consistent chain source makes the reported count more stable.

Compare an observation with the 450-BTC baseline

Once the date, chain, block count and coinbase method are stated, the difference from 450 becomes interpretable. A 143-block full-subsidy example gives 446.875 BTC; a 145-block example gives 453.125 BTC. The long-run ten-minute target makes 144 a handy average, while actual short windows vary. The comparison tells us about block frequency during that reporting window, not whether bitcoin's price must change.

A daily mined total is also not the day's newly available market inventory. Miners may hold their new BTC or sell it, and existing holders can trade old coins. The audit measures network creation. It says nothing by itself about who sold, which exchange received deposits, or whether mining was profitable after costs.

For a quick answer in the current era, use “roughly 450 new BTC per target-paced day.” For an actual date, record UTC boundaries, accepted block heights, subsidy in satoshis, fees separately and any underclaimed amounts. That makes the phrase “how many bitcoins are mined per day” a measurable statement instead of a number copied from a dashboard without its definition.