Are we mining the already found block?
Slush's stat page shows that we are mining 254832, however according to BTC Guild, this was already found by them:
19306 254832 2013-08-29 08:23:07 PM 8c7866382409677faee120b9c26bda0221a850fe9bfb3b6317496a927247c8ae 25.01180001
This is consistent with blockchain.info
Is that why we are stuck for more than 8 hours? "barking up the wrong tree"?!
No.
The page is showing which is the latest block it knows about, not the one we are working on.
At the moment, its showing 254837, which is the latest one, found by deepbit.
Even if we were working based on a too old block, this would not prevent us from eventually finding a share and going on with the next round. That found block would end up being invalid, but we would not be stuck. The current 10 hour round is, depending on how you want to see it, either just bad luck or totally probable within the variance caused by the systems. (Don't get me wrong, its quite unlikely for a round to last 10 hours - as you can see via CDF statistics, its only 0.3 %, but its very likely that at least some of our many rounds last that long.)
Usually the block shown in stats has the block number which has not been solved yet (last block shown on blockinfo.org for example + 1), what happened now is that Slush's pool was trying to solve a block that has already been solved by another pool. It is not clear how solving the previous block would lead us to the next one...
right now
Height Age Transactions Total Sent Relayed By Size (kB)
254841 3 minutes 559 7,093.70 BTC 82.28.96.243 224.09
and Slush's stats says: Current Bitcoin block, difficulty: 254841, 65750060
so again it looks like we are out of synch with the network
(bfgminer shows the next block number, in case we do not trust blockchain.info)
Show Posts
