Bitcoin Difficulty Fell 3.34% at Block 895,104

Bitcoin’s proof-of-work difficulty fell 3.34% at block 895,104 on May 4, 2025, ending four consecutive upward adjustments and giving miners a modest automatic easing of the requirement applied during the new 2,016-block period.

The block record carries a header timestamp of 05:00:13 UTC. The compact target encoded in the block corresponds to a difficulty of approximately 119,116,256,505,724, commonly shortened to 119.12 trillion, down from 123,234,387,977,050. Using those two difficulty values, Coinburn calculates the change as negative 3.3417%, rounded to negative 3.34%.

This was a protocol event, not a committee decision or miner vote. Every validating node applied the same proof-of-work rules when evaluating the block. The adjustment therefore established a less restrictive valid target for the network once block 895,104 entered the best chain.

What the adjustment measured

Bitcoin aims for an average interval of about 10 minutes between blocks. Its rules reassess the proof-of-work target every 2,016 blocks using timestamps from the preceding adjustment period. When that period runs faster than the target duration, difficulty rises; when it runs slower, difficulty falls.

The 3.34% decline indicated that the completed period had run more slowly than the protocol’s target. It did not mean the network had lost exactly 3.34% of its computing power at the adjustment moment. Hashrate is not directly reported by miners to a central authority; data services estimate it from observed block production and difficulty, and short-window estimates can swing because block discovery is probabilistic.

Difficulty is also a unitless ratio relative to Bitcoin’s easiest reference target. Calling 119.12 trillion the number of guesses required to find a block would be inaccurate. The expected number of hash attempts is much larger and remains a probability, not a guaranteed workload for any miner.

Why it mattered to miners

For a miner holding its hashrate constant, lower network difficulty improves expected bitcoin production over a fixed period, all else equal. That made the May 4 reset a measure of operational relief after four increases beginning March 9 had raised the competitive requirement.

The relief was limited. Difficulty does not determine electricity prices, machine efficiency, financing costs, uptime, transaction fees or bitcoin’s dollar price. An easier target can improve expected bitcoin-denominated production per unit of hashrate while an individual operator’s dollar margins still worsen for unrelated reasons.

The adjustment also illustrated the distinction between network security and a single headline metric. A decline in difficulty reduced the work expected for each block relative to the preceding period, but it did not by itself establish that Bitcoin was unsafe or that miners were abandoning the network. Evaluating security would require a defined hashrate window, chain-work comparisons and evidence about the cost and distribution of mining capacity.

What was knowable on May 4

Contemporaneous reporting on May 4 identified the same block height, old and new difficulty levels, and the first downward move after four increases. Estimates published that day placed network hashrate near 885 exahashes per second, but such figures depended on the provider and averaging window. Coinburn therefore treats 885 EH/s as an event-day estimate, not an on-chain measurement.

The durable fact was narrower: block 895,104 encoded an easier proof-of-work target, and the derived difficulty fell 3.34% for the next adjustment period. Forecasts about the following retarget were not facts on May 4 because subsequent block times and deployed hashrate could change them.

The block header’s timestamp is miner-supplied and constrained by consensus rules rather than certified by an external clock. Even with that limitation, the 05:00:13 UTC header time, the block’s chain position and contemporaneous May 4 reports support dating the adjustment to May 4, 2025.