Yup, 18702 needs a recalc

18702    2013-06-22 15:21:37    1:59:11    30464457    5986    0.00000107    242788    25.44442180    88 confirmations left

its a jjoke

Partybreaker!

Same problem here. First thought: WTF!

18703   2013-06-22 16:17:50   0:56:13   14180802   21402   0.03703753   242797    25.39405000    93 confirmaties te gaan
18702   2013-06-22 15:21:37   1:59:11   30464457   49165   0.00000675   242788    25.44442180    84 confirmaties te gaan
18701   2013-06-22 13:22:26   1:54:50   29531738   47391   0.04113149   242773    25.92630343    69 confirmaties te gaan

Get more? How? Please share with us.

I get 334 MH/s average with all my sticks.

Theoretical max. is 336 MH/s because they run at 336 Mhz. You must be overclocking right? 

Didn't know that. So it is probably display error. After running for a day I can see them from 333 to 339 depending on unit but not every time the same unit and not every time. I just cool them... Nothing special...


EDIT: But now that I look at them I see most of them running 335.3 to 335,7 so I guess you are right and 339 is just a display bug that some error is causing...

I see it back to normal too,
But, I want to know why this happen,and how to make it never happen again?

Hey Guys, just playing around with an Erupter before my Jalapeno comes and I'm curious:

Running Cgminer on Minepeon (Raspberry Pi) I'm measuring 330 MH/s (via the web GUI) but on the Slush website, I'm getting 208 MH/s (which has slowly been rising from the 130 from 25 minutes ago.)
Is this normal, like does it take time to get things in sync or   (When I tested the Erupter on my desktop with Bitminter, I got 333 MH/s via their app. right away)
I am connected via Stratum btw.

Thanks,
IAS

edit - Just noticed this under the stats - "* The calculation is based on the number of shares so far, which may not be accurate for slow workers."
So, does this mean I'm actually only "getting paid" for the 208MH/s or

the hash rate on the Slush sight rarely reflects what your actual hash rate is, sometimes it is higher and sometimes lower, on average it is close to being right.

Well if you don't have backup pool taking pool offline would do it. Also rejecting all shares if you don't have settings in the config for miner to jump to backup in this case. Not recording shares will also do it. Technically last two would change hashrate only on server side. Other then that I can't think of a way...