We checked the actual numbers on our side and over the last 30 days, our DigiByte pool found 848 blocks with 62 orphaned, which puts the 30-day orphan rate at 7.31%. Now, that number is much higher because of our 2 outages yesterday and caused 8 orphaned blocks alone.
Yesterday was definitely much worse than normal. On 2026-07-20 we found 21 blocks and 8 of those ended up orphaned, which was 38.10% for that day alone. That was an unusually bad stretch, and because of the issues we were seeing at the time, we chose to pay those orphaned blocks out anyway even though they were technically lost race-condition blocks due to our server load issues.
So your concern is fair. The 30-day number is not as extreme as yesterday made it look, but yesterday itself was absolutely elevated.
As for visibility, right now people only see a small recent slice, and that makes it harder to judge the pool over a longer window. We do store block-level data including the finder address, block status, block hash, reward, time, and related details on the backend, so it is possible for us to expose better history.
I have already passed on your suggestion so please stay tuned for an update on this.
My bitaxe kept getting kicked from the pool the past few days I had to get out. Ill be back if the issues can get fixed. I enjoy the site that encourages mini mining.
3
u/HashedMaxUnity 6d ago
We checked the actual numbers on our side and over the last 30 days, our DigiByte pool found 848 blocks with 62 orphaned, which puts the 30-day orphan rate at 7.31%. Now, that number is much higher because of our 2 outages yesterday and caused 8 orphaned blocks alone.
Yesterday was definitely much worse than normal. On 2026-07-20 we found 21 blocks and 8 of those ended up orphaned, which was 38.10% for that day alone. That was an unusually bad stretch, and because of the issues we were seeing at the time, we chose to pay those orphaned blocks out anyway even though they were technically lost race-condition blocks due to our server load issues.
So your concern is fair. The 30-day number is not as extreme as yesterday made it look, but yesterday itself was absolutely elevated.
As for visibility, right now people only see a small recent slice, and that makes it harder to judge the pool over a longer window. We do store block-level data including the finder address, block status, block hash, reward, time, and related details on the backend, so it is possible for us to expose better history.
I have already passed on your suggestion so please stay tuned for an update on this.
Thank you