Ok, I figured out what happened with the explorer. I sync'd a preliminary change to github for version 1.0.3.0 that had to be fixed. 1.0.4.0 fixed the problem, I created the commit, and built the wallets, and did the whole announcement, but I ended up syncing the change to the wrong (testing) branch.
All your wallets are fine. If you're stuck on a block before 10348 you'll need to delete your blockchain stuff and resync.
Basically anyone that compiled off the github got a slightly outdated copy of the code, and they staked with the new code creating a fork. No one running on the windows wallets should have any issue, and people on linux will get back on the right chain once they compile the latest source. Sorry >.<
Once again thanks for the hard work and effort put into this. When will the block explorer be back on the correct block?
As soon as they update it. It's actually a little funny, since the fork is only two blocks long. 10330 is correct. Forked at 10331.
when will the block explorer get fixed?
Asap, I've contacted them via twitter and pm. We're working on it.
In the meantime
/Satoshi:1.0.2/ 60013 124 63.3 % 63.3 %
/Satoshi:1.0.4/ 60013 33 16.8 % 80.1 %
/Satoshi:1.0.1/ 60013 31 15.8 % 95.9 %
/Satoshi:1.0.0/ 60013 5 2.6 % 98.5 %
/Satoshi:1.0.3/ 60013 3 1.5 % 100.0 %
That's the current distribution of wallets. People running 1.0.0, well... they've forked off into oblivion already. 1.0.2 is the old wallet that will be useless in about 6 hours. 1.0.3 is wallets that were compiled with the testing source that didn't get updated properly.
I'm trying to make sure bittrex isn't one of those three as well. If they are you can't send or receive coins from bittrex either. I might be one of the three, as I ran the 1.0.3 wallet recently enough to show up on that list, one is the explorer itself, and one is the person who staked off the github source at the time.
Still, there's a LOT of 1.0.2's
If you're not running 1.0.4, please update ASAP