Quote from: kano on February 03, 2018, 05:19:57 AM

Quote from: Biodom on February 03, 2018, 05:08:39 AM

Quote from: kano on February 03, 2018, 03:12:18 AM

Quote from: Biodom on February 03, 2018, 02:09:15 AM

Quote from: kano on February 03, 2018, 01:25:39 AM

Quote from: Biodom on February 02, 2018, 11:43:58 PM

...
Are you saying that we will see the final data for January ONLY when we will see the first block in February OR that the current posted data for January IS already final. If it is not final, maybe explain why not? Thanks.

The monthly blocks table is for blocks found in the month.
We won't find any more in January - so it's final.

I probably don't get how the the stats are being displayed.
It could be entirely my misunderstanding of some params.

Specifically, 21.68 ph in dec, 31.98 ph in Jan, 22% increase in Ph.
expected blocks: 6.8 in January vs 10.2 in Dec, a 32.7% decrease
Hashing power went up 22%, expected blocks decreased 32.7%
Yet, the network hashing power had the arithmetic average of 12.88 Zetah/s in Dec vs 18.56 Zetah/s in january, a 44% increase
I can't match the numbers with roughly 10% mismatch.

The first block each month includes shares mined at the end in the previous month after the last block found.
How much it overlaps depends on luck and pool hash rate.

Edit: yeah and difficulty as mentioned by Mr.Joe

(each month has 2 or 3 diff changes)

First off, I allowed for difficulty change as I specifically mentioned in my post.

Second, no way our numbers for January are those that are currently on the website.
As you say, they will be adjusted once the first block in February is found.
I expect the number at around 100%, maybe even lower, but NOT 116%.
116% number was there since the last block and it did not budge the week (or so) without blocks.
I fail to see the relevance of this number in such case.

The January number wont change.

As I said, it shows the stats for blocks found in January - not the hashing done in January.
The code works as: any block with a date of the month of interest, then it's numbers are included in the calculation for a given month.
The hash rate is easy:
Elapsed = from the time of the last block of the previous month to the time of the last block of the current month.
Hashes done = total hashes of each of the blocks in the month (including invalids before them of course)
Hash rate = Hashes done / Elapsed

The next block found will be in February, so that wont affect the January numbers.

OK, I think I finally got it.
Thanks for the detailed explanation, it was helpful.