Quote from: smutboy420 on December 16, 2017, 03:09:26 AM

Quote from: kano on December 16, 2017, 02:50:59 AM

Quote from: smutboy420 on December 16, 2017, 02:21:21 AM

...
Cool beans kano. looking at the time pool 10 detected a new block "[2017-12-15 18:31:22.953] Stratum from pool 10 detected new block at height 499476" with the time that slush pool finised the block 499476 and got it relayed in was at 18:31:17 so its looking like it only tool a few millseconds less then 6 seconds for the pool to be geting cracking on new work. from the time slush got the block before that relayed in. Thats seem pretty darn quick. but if I happen to be looking at the right moments again and notice any big discrepancies in the time displayed on the top of the kanopool page I will try to take note of how much the time is off if I happen to notice again.

No, 6 seconds is WAY too slow.

But I suspect you are misreading that time.
The time in the block is not when it was found.
Block 499476 has a date stamp of "2017-12-15 18:31:17" which is the (somewhat random) time put in the block header, not the time the block was found, and certainly not the time that pool processed the block.

If it was, then that would mean that slush is slow to distribute their blocks.

All our node's bitcoinds processed the block during the second of "2017-12-15 18:31:22"

That very well could be that slush is slow. They have been going threw some sort of DDoS attack for about the last week or so more then even normal. and there page some times wont refresh or will pop up with a Cloudflare notice quite a lot.

But for what is worth they hit another block about 20 mins ago and I happened to notice it when they were about 12 mins in to the next block and kanopool info was showing it being 2 mins in to the next block and so I put the 2 pages next to each other and hit refresh on kano and then I took a screen shot for you so you can see what I mean. and got it just in the nick of time because only a few seconds later someone some were found that block and then it was on to the next one when I refreshed the kano page again.

http://i65.tinypic.com/2lwt834.jpg

Well I don't know what is causing that for you - but again you'd need to check the UTC time in the bottom left and make sure your ISP or connection isn't caching old data.

We found 498508 at 2017‑12‑10 03:39:29
Add 143hrs and 14m gives 2017‑12‑16 02:53:29 - so the time you got that page would be around 02:53:29 give or take a minute due to the "143hrs and 14m" rounding.

That's 3 mins and 20 seconds after block 409532 plus or minus a minute.
Network there says 2:51 since last block which fits into 3:20 + or - a minute.

So your web page matches what you would expect to see at about 2017‑12‑16 02:53:29 (plus or minus a minute)