user3165: Where does the data come from?


user13866: The total network hashrate can be estimated from the network difficulty recorded in the block headers over a reasonable sample period.
There is a relationship between the two because the difficulty is adjusted every 2016 blocks (about two weeks at 10 minutes per block) with the aim of keeping block production rate near constant as total network hashrate changes.
See How can I calculate network hashrate for a given range of blocks where difficulty changes somewhere within the range? for calculation

user5406: As RedGrittyBrick already wrote, the difficulty to create new blocks is adjusted every 2016 blocks. The difficulty provides an expected amount of hashes performed to find a block, which allows a general estimate how much hashrate exists on the network. Additionally, some websites compare the number of published blocks with the expected number of blocks found to provide a higher resolution than whole difficulty periods. Since blocks are found in a random process, these charts often jump around a lot as even a constant hashrate can have a large variance of blocks found per day.
As an example, let's take a look at this chart of Blocks per Day for the last three months. The blocks found range from 89 on 2022-12-24 to 180 on 2023-01-06.  
via transactionfee.info
Meanwhile, the self-reported hashrate of mining pools in the last three months looks like this: 
via miningpoolstats.stream
While we do see a drop in the self-reported hashrate on Christmas Eve (partially explained by an extreme winter freeze in Texas that had miners yield power for heating homes) that aligns with the lowest block count, the self-reported hashrate ranges between 200 EH/s and 287 EH/s while the block count maximum is double the minimum.
This is underscored when we compare the self-reported figures with miningpoolstats.stream's estimated hashrate on the network:
via miningpoolstats.stream
So, the hashrate can be estimated from the difficulty of the blocks and the count of blocks found, but the random process makes it easy estimate much larger swings than seem to be present in the actual hashrate.

3165: <p>Where does <a href="https://bitinfocharts.com/comparison/hashrate-price-btc.html#1y" rel="nofollow noreferrer">the data</a> come from?</p>
<p><a href="https://i.stack.imgur.com/3wACo.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3wACo.png" alt="enter image description here" /></a></p>
 13866: <p>The total network hashrate can be estimated from the network difficulty recorded in the block headers over a reasonable sample period.</p>
<p>There is a relationship between the two because the difficulty is adjusted every 2016 blocks (about two weeks at 10 minutes per block) with the aim of keeping block production rate near constant as total network hashrate changes.</p>
<p>See <a href="https://bitcoin.stackexchange.com/q/14086/13866">How can I calculate network hashrate for a given range of blocks where difficulty changes somewhere within the range?</a> for calculation</p>
 5406: <p>As RedGrittyBrick already wrote, the difficulty to create new blocks is adjusted every 2016 blocks. The difficulty provides an expected amount of hashes performed to find a block, which allows a general estimate how much hashrate exists on the network. Additionally, some websites compare the number of published blocks with the expected number of blocks found to provide a higher resolution than whole difficulty periods. Since blocks are found in a random process, these charts often jump around a lot as even a constant hashrate can have a large variance of blocks found per day.</p>
<p>As an example, let's take a look at this chart of Blocks per Day for the last three months. The blocks found range from 89 on 2022-12-24 to 180 on 2023-01-06.  <a href="https://i.stack.imgur.com/OaqGk.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/OaqGk.png" alt="enter image description here" /></a><br />
<sup>via <a href="https://transactionfee.info/charts/blocks-per-day/?start=2022-10-12&amp;end=2023-01-11" rel="nofollow noreferrer">transactionfee.info</a></sup></p>
<p>Meanwhile, the self-reported hashrate of mining pools in the last three months looks like this: <a href="https://i.stack.imgur.com/e3tZm.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/e3tZm.png" alt="enter image description here" /></a><br />
<sup>via <a href="https://miningpoolstats.stream/bitcoin" rel="nofollow noreferrer">miningpoolstats.stream</a></sup></p>
<p>While we do see a drop in the self-reported hashrate on Christmas Eve (partially explained by an <a href="https://news.abplive.com/business/crypto/bitcoin-s-hash-rate-down-texas-restricted-hash-power-miners-massive-winter-freeze-1571915" rel="nofollow noreferrer">extreme winter freeze in Texas that had miners yield power for heating homes</a>) that aligns with the lowest block count, the self-reported hashrate ranges between 200 EH/s and 287 EH/s while the block count maximum is double the minimum.</p>
<p>This is underscored when we compare the self-reported figures with miningpoolstats.stream's estimated hashrate on the network:<a href="https://i.stack.imgur.com/dE68E.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dE68E.png" alt="enter image description here" /></a><br />
<sup>via <a href="https://miningpoolstats.stream/bitcoin" rel="nofollow noreferrer">miningpoolstats.stream</a></sup></p>
<p><strong>So, the hashrate can be estimated from the difficulty of the blocks and the count of blocks found, but the random process makes it easy estimate much larger swings than seem to be present in the actual hashrate.</strong></p>
