pull down to refresh
20 sats \ 4 replies \ @cryptocoin 4 Oct 2022 \ on: New Hashrate ATH 271.9258 EH/s bitcoin
Variance happens.
Depending on your time frame, you could probably find where hashrate has already been well over 30,000 EH/s.
30,000! What!!!?, you might ask?
Has there ever been two blocks within five seconds of each other. Yes? Ok, so that's an example of a block being solved 120X faster (600 / 5 = 120) than expected. If the hashrate for the current difficulty is 250 EH/s, that would mean 250 EH/s X 120 = 30,000 EH/s!
So that's why we don't determine hashrate using the time from one block to the next. I don't know the time duration of bitinfocharts' hashrate page for "Raw values", but it is definitely too short to provide any useful information.
Change the "Technical Indicators" dropdown to show "Simple Moving Average" and leave the Period to 7-day, and then a closer estimate of hashrate shows 242 EH/s. That is a lot more realistic than 271 EH/s.
On the one hand you suggest hashrate is "probably" higher based on a block to block examination and then on the other hand you suggest that the daily hashrate is not accurate enough, must use 7 day average. :)
reply
On the one hand you suggest hashrate is "probably" higher based on a block to block examination
I did no such thing. I pointed out how meaningless it is to use a short timeframe when trying to estimate hashrate.
Hashrate doesn't jump much day to day. It technically could bump up a bit (e.g., 2%) in
a day if a very large mining farm were to become energized all at once (which they don't necessarily do it that way), but then the hashrate would stay at that higher level. What that "raw values" chart is showing is variance. Essentially that "raw values" view is meaningless as an indication of actual hashrate increase or decrease.
reply
Yeah, you did exactly that. It's all in your first comment. I don't care that much, it's just an interesting observation.
reply
Ok,... firstly there is no such thing as a hashrate measurement. There is a difficulty data point, and a hashrate estimate can be derived from that. But that difficulty data point only changes every 2,016 blocks.
So every single claim of the hashrate level is an estimate. I can use a timeframe that is just a specific few seconds and from that data claim that the hashrate estimate has suddenly increased 100X from its level just before. But I would be seen a fool, as everyone knows the difficulty will not be increasing 100X from one moment to the next.
If you want a sensible estimate, use a more sensible timeframe, like 7 days. That's all I'm saying.
reply