The website for the block explorer only says; "Working " instead showing that explorer.
As you can see below the blocks (in green) are spaced correctly and then difficulty (BOLD) rockets to 245 and then 578.
104 26 left momocoin 09/22/2014 07:30:12 578.5844 50.00 148,118 181,484 122.53
102 24 left hitton 09/22/2014 06:46:21 578.5844 50.00 148,118 78,796 53.20
101 23 left britcoin 09/22/2014 06:40:14 578.5844 50.00 148,118 482,787 325.95
85 7 left andresmir 09/22/2014 05:33:48 245.2485 50.00 62,784 162,755 259.23
76 Confirmed andresmir 09/22/2014 05:13:53 53.5193 50.00 13,701 33,314 243.15
74 Confirmed andresmir 09/22/2014 05:12:56 53.5193 50.00 13,701 26,295 191.92
72 Confirmed andresmir 09/22/2014 05:12:21 53.5193 50.00 13,701 50,478 368.43
70 Confirmed batica 09/22/2014 05:09:59 53.5193 50.00 13,701 1,854 13.53
68 Confirmed jackstraw 09/22/2014 05:09:45 16.0000 50.00 4,096 15,869 387.43
63 Confirmed Z 09/22/2014 05:07:00 16.0000 50.00 4,096 5,703 139.23
61 Confirmed d33 09/22/2014 05:04:53 4.0000 50.00 1,024 597 58.30
59 Confirmed Mrbee 09/22/2014 05:04:23 4.0000 50.00 1,024 122 11.91
58 Confirmed TheWanderer 09/22/2014 05:04:10 4.0000 50.00 1,024 833 81.35
Well, without the corresponding net hashrate ...
85 - 101 = 16 blocks 1h 7m diff moving from 245.2485 to 578.5844
101 - 102 = 1 block 6m diff at 578.5844
102 - 104 = 2 blocks 44m diff at 578.5844
That spike is indicating a max hashrate ~ 16 GH and the skyrocketing block times at still the same high diff show the retargeting down did not happen at that time. I saw the diff falling later to 140 for a moment before it went back to over 200 without a corresponding short drop of hashrate on the pools.
official pool:
pool hash 1.2 GH
net hash 2.5 GH
suprnova:
pool hash 5.6 GH
net hash 5.6 GH
The estimation for the next diff is far off on both pools.
At the moment the hashrate looks sort of stable around 7 GH (taken from those 2 pools) and the diff of 245 seems to roughly fit.
If this coin becomes successful and switching pools jumping in and out, you will see steady spikes in hashrate and than leaving the normal miners with high diff and endless blocktimes until the diff finally comes down again and the pools will jump in again until the diff spikes ....
DGW3 is supposed to react in those cases of hashrate spikes very fast (retarget every block) with a quick rise and even quicker fall of diff, but within a certain change limit per block.
What I am seeing here is, that the diff stays high (at the same number) far longer than it should with DGW3 and proper set numbers for this coin.
Link to the source of this coin?
