Markets
BTC— —
ETH— —
SOL— —
XRP— —
BNB— —
ADA— —
DOGE— —
MCap— —
BTC— —
ETH— —
SOL— —
XRP— —
BNB— —
ADA— —
DOGE— —
MCap— —
Tech

Slower Blocks Cut Bitcoin Difficulty 9.13%, Deeper Than Forecast

The cut at block 975,744 ran deeper than the 6.8% to 7.5% forecasters had projected, because computing power kept leaving the network through the second half of the period. Difficulty is still about 8% above where June's larger cut left it.

By MiningPool Staff··4 min read
Slower Blocks Cut Bitcoin Difficulty 9.13%, Deeper Than Forecast

Key Points

  • The cut at block 975,744 ran deeper than the 6.8% to 7.5% forecasters had projected, because computing power kept leaving the network through the second half of the period.
  • Difficulty is still about 8% above where June's larger cut left it.

Bitcoin's mining difficulty fell 9.13% at block 975,744, dropping from 148.36 trillion to 134.82 trillion in the network's largest downward adjustment since June. ChainCatcher reported the retarget early on Saturday, citing data from CloverPool, and The Defiant published the same percentage and block height about an hour later.

The adjustment is automatic. Bitcoin resets difficulty every 2,016 blocks to steer the average time between blocks back toward 10 minutes, so the size of each change is a direct measure of how slowly the previous 2,016 blocks arrived. Running that formula backwards, a 9.13% cut means the period took about 15.4 days against the 14-day target, an average of 11.0 minutes a block. The Defiant reported separately that blocks had been averaging roughly 11 minutes, which matches the figure the percentage implies.

The cut came in deeper than the forecasts. A November 10 analysis by DCForecasts put it at about 6.8%, to roughly 138.3 trillion, measuring the period's running block interval at about 10.7 minutes at that point. CryptoTicker, working from mempool.space's estimate two days later, projected about 7.5% and recorded blocks averaging 10 minutes and 49 seconds since the October 29 adjustment. A November 2 MillionMiner update had put early estimates for the same block between a 1.7% cut and a 4.3% increase. The actual adjustment was 2.3 percentage points below the November 10 projection, and about 3.5 trillion lower than the difficulty it implied.

Advertisement

728×90

The gap follows from the block times themselves. The running average interval was about 10.7 minutes on November 10 and 10 minutes 49 seconds on November 12, and the completed period averaged 11.0 minutes, so blocks in the closing stretch must have arrived more slowly than those before them. Computing power was still leaving the network in the final days, and CryptoTicker recorded the seven-day average hashrate falling to 979 exahashes per second in the week to November 9. On the standard conversion of difficulty to the hashrate needed to hit 10-minute blocks, 134.82 trillion implies a period that averaged about 965 EH/s, against the roughly 1,062 EH/s the previous setting was calibrated for.

Bitcoin's price fell across the same period, which The Defiant's report put behind the squeeze on miners. CoinDesk recorded bitcoin as low as $67,652 at 09:17 UTC on November 13, down more than 3.5% over the previous 24 hours and about 16% over the month, with the 200-week moving average sitting near $68,000. By 16:03 UTC the same day it had the price at $68,750 and down more than 21% for 2026. MiningPool reported bitcoin falling to about $73,761 late on November 8, so a substantial part of the decline landed inside the period that just closed.

For the machines still running, the cut raises expected revenue per unit of computing power by about 10%, which is what a 9.13% reduction works out to if the bitcoin price and transaction fee revenue hold still. Neither held still. The price fell across the same two weeks, so the practical effect on daily revenue is smaller than the mechanical figure, and how much smaller depends on where the price settles. MillionMiner put hashprice at $33.26 per petahash per second a day on November 2, before both the decline and this retarget, with no later reading available.

June's larger cut left difficulty lower than this one has. MiningPool reported difficulty falling 10.09% at block 953,568 on June 14, from 138.96 trillion to 124.93 trillion, after a period that took 15.6 days. That cut was larger, and 124.93 trillion is about 7% below where this adjustment has put it. The network is still harder to mine than it was at the June low, and bitcoin was in the low $60,000s around the June cut against the $68,750 CoinDesk recorded on November 13.

Both descriptions circulating of this cut are accurate. ChainCatcher called it the largest single decrease since the 10.09% adjustment on June 14, which it is. The Defiant called it the year's third-largest, which also holds: MiningPool recorded June's cut as the second-largest negative adjustment of 2026 at the time it happened, so one earlier cut this year was bigger still, and a 9.13% reduction ranks behind both.

Where the capacity went is a question the retarget cannot answer on its own. Network hashrate is inferred from how fast blocks arrive rather than measured directly, so every published hashrate figure is one provider's calculation over a chosen window. Difficulty is the part recorded on the chain. What the chain does not show is whether the machines that stopped were switched off because the price made them unprofitable or pointed at other work. Listed miners have spent the year converting power contracts and sites to artificial intelligence and high-performance computing, and MiningPool reported in October, citing BlocksBridge Consulting, that the sector's recovery past one zettahash had come alongside a 23% decline in realized hashrate among public miners and a 52% quarterly rise in their directly reported AI revenue.

The next adjustment comes 2,016 blocks later, at block 977,760, which at the ten-minute target would fall around November 27 and later if blocks keep running slow. Difficulty rose at each of the two retargets before this one, 5.92% on October 16 and 5.54% on October 29, and whether it rises again depends on how much of the computing power that came off in the past two weeks returns at the lower setting.

MiningPool content is intended for information and educational purposes only and does not constitute financial, investment, or legal advice.

Advertisement

728×90

Related Stories

BitGo Says Unocoin's Own Two Keys Signed the Disputed Transfers
Tech

In a two-of-three self-custody wallet, the user and backup keys Unocoin holds can sign without BitGo's key and be broadcast straight to the chain, which is why a working account freeze and an unauthorized outflow are not a contradiction. Unocoin says it has not established how the keys were accessed, and neither company has published a loss figure.

·MiningPool Staff
A Bitcoin Core Bug Could Stop Mining Nodes From Building Blocks
Tech

The high-severity flaw, disclosed on November 10 alongside two medium ones, left an affected node unable to produce a valid block template until it was restarted. The fixes shipped in October 2025, and the advisories waited until the last vulnerable release line lost support.

·MiningPool Staff
Web3Auth Published Recovery Addresses That Bitquery Tied to a Thief
Tech

Web3Auth says 12 addresses hold crypto it moved out of vulnerable Keplr wallets, and the eight that Bitquery had identified a day earlier as a thief's collection wallets are among them. The provider used the attacker's own route, so the published totals describe overlapping holdings rather than separate pools.

·MiningPool Staff
Gnosis Pay Breach Notices List Card Numbers and Wallet Addresses
Tech

Gnosis Pay's public notice said only that certain customer information was exposed. The notices sent to affected customers listed full card numbers with CVV codes alongside the wallet addresses linked to their accounts, according to notifications reviewed by Cointelegraph.

·MiningPool Staff

Stay informed

Verifiable crypto journalism, delivered to your inbox.

Weekday mornings. No hype. No financial advice. Just what happened and why it matters.

No spam. Unsubscribe anytime. Read our privacy policy.