Please all pool owners and solo miners, check your daemon logs now, we stuck again.
It seems that some bug in miner.
Might be coincidence -
I restarted my mining daemon to be able to print_block and see what was going on, and found the next block very shortly thereafter.
I'm *sure* that the latter part was luck - it's a very fast machine but not *that* fast - but I wonder if there was something about the restart that triggered some updates.
The only things I notice about the blocks:
The "extra" field in 16755 is larger than any of the previous several blocks;
16756 included two tx hashes, which none of the previous blocks did.
16756 "timestamp": 1402428976,
16755 "timestamp": 1402425579, <- last block found before the gap
16754 "timestamp": 1402425570,
...
And extra fields:
16756 "timestamp": 1402428976,
"tx_hashes": [ "9d0367bd319b128856c4b5c0039d81d77da14594753f849a4b2cff25642e43b2", "5f52cc1f3922edaaccac6a226b0c1db4981952c2ead97550c80ba27d8a4bf031"
"extra": [ 1, 12, 170, 236, 106, 246, 128, 1, 64, 237, 160, 188, 139, 26, 60, 183, 2, 138, 33, 11, 78, 91, 223, 3, 160, 14, 147, 223, 31, 190, 15, 162, 14, 2, 22, 48, 46, 49, 46, 49, 46, 57, 40, 48, 46, 49, 45, 103, 101, 54, 50, 50, 99, 97, 48, 41, 124
16755 "timestamp": 1402425579,
"extra": [ 1, 254, 90, 32, 214, 169, 66, 142, 107, 82, 112, 69, 141, 195, 9, 6, 153, 36, 236, 134, 174, 29, 214, 163, 233, 119, 179, 189, 81, 22, 225, 246, 0, 2, 32, 48, 46, 49, 46, 49, 46, 49, 49, 40, 51, 48, 49, 55, 52, 102, 50, 45, 100, 105, 114, 116, 121, 41, 0, 0, 0, 0, 7, 89, 162, 98, 0
16754 "timestamp": 1402425570,
"extra": [ 1, 28, 48, 231, 241, 73, 242, 252, 185, 15, 227, 86, 12, 140, 79, 7, 171, 166, 109, 180, 100, 186, 97, 81, 74, 6, 20, 191, 82, 131, 53, 136, 111, 2, 22, 48, 46, 49, 46, 49, 46, 57, 40, 48, 46, 49, 45, 103, 101, 54, 50, 50, 99, 97, 48, 41, 124
The second of those two tx hashes was a pretty large transaction.