I noticed an oddity in the block explorer...
24644 2014-03-21 05:12:09 7 18.18658015 22.662 2591660.8 20.5815 35.554 20.7499%
24643 2014-03-21 05:10:11 1 3.72 22.633 2591657.08 20.5802 35.5526 20.751%
24642 2014-03-21 05:10:36 3 4.8530764 22.548 2591653.36 20.5805 35.5529 20.7508%
24641 2014-03-21 05:10:12 1 3.72 22.524 2591649.64 20.5802 35.5526 20.751%
24640 2014-03-21 05:10:17 1 3.72 22.532 2591645.92 20.5803 35.5527 20.751%
24639 2014-03-21 05:06:59 3 16.61846048 22.596 2591642.2 20.5781 35.5504 20.7528%
24638 2014-03-21 05:01:52 5 11.86976141 22.595 2591638.48 20.5745 35.5468 20.7556%
24637 2014-03-21 05:00:47 1 3.72 22.648 2591634.76 20.5738 35.5461 20.7562%
24636 2014-03-21 04:57:02 1 3.72 22.644 2591631.04 20.5712 35.5435 20.7583%
To simplify that... (Reversed the order to reflect actual passing time. Top to bottom.)
Block 24637 found at 05:00:47
Block 24638 found at 05:01:52 (Ok, about 1 minute later, good luck)
Block 24639 found at 05:06:59 (Ok, about 4 minutes later, bad luck)
Block 24640 found at 05:10:
17 (Ok, about 3 minutes later, bad luck still)
Block 24641 found at 05:10:
12 (Um, -05 sec! That's fast, 24641 was found before 24640!)
Block 24642 found at 05:10:
36 (Ok, about 24-19 sec later, great luck!)
Block 24643 found at 05:10:
11 (Holy shit! -25 sec earlier! Even before block 24640!)
I thought the clocks demand forward-only time, rejecting times that are off-set improperly. Or does this ignore the seconds?
P.S. That's a hell of a lot of luck all at once. Not sure what impact negative values has on the gravity-well adjustments.
Another sample...
24657 2014-03-21 05:44:23 7 20.72150741 22.456 2591709.16 20.6035 35.5764 20.7321%
24656 2014-03-21 05:43:52 2 6.72081359 22.438 2591705.44 20.6031 35.576 20.7324%
24655 2014-03-21 05:43:15 1 3.72 22.374 2591701.72 20.6028 35.5756 20.7327%
24654 2014-03-21 05:43:57 2 5.17492861 22.363 2591698 20.6033 35.5761 20.7324%
24653 2014-03-21 05:41:23 7 45.9938255 22.413 2591694.28 20.6015 35.5743 20.7338%