Or am I missing something?
Are you running 0.15.4 ? If so, this issue should be alleviated when a block is found. The issue as I understand it is that since a block hasn't been found recently enough, the client thinks that there are missing headers when in reality the latest block is just 'behind schedule'. If not, upgrade and let us know whether this helps.
Yep. 0.15.4 is the only one I could find easily--it was right on the website.
The thing is, though, yesterday morning I woke up with the explorer at 23205 and went to bed with it at the same position. This morning, I woke up to it at 23330. There are plenty of blocks with timestamps all through the day between the timestamps of block 23205 and 23330. In fact, the time between block 23205 and 23206 is ~4 hours but I didn't see that until this morning. The explorer has been stuck at 23330 all day today as well.
Hrm - well, deleting your blockchain database and re-syncing _might_ solve the issue, but let me bring this to the attention of the wallet devs to make sure I don't put my foot in my mouth here.
Thanks for your patience.
I'm not so much concerned about my desktop wallet (it'll sync when it syncs). But when the actual explorer website is stuck on the same block (like right now it's been stuck at 23330 for well over 24 hours) I get a little concerned.