It's been already in different thread, but gets not enough attention, so let's make a new thread.
In 0.5.x there's special account, can you find it?
big HINT: the account is in NEMESIS BLOCK.
First block hash: ec188749598a6e573815a6226b778001066936ebd86569311c527045d872cbbf
Doesnt help me^^
or you could try typing "block 1" in search box 
You have a multisig account in there .
TBONKWCOWBZYZB2I5JD3LSDBQVBYHB757VN3SKPP
It has a very simple private key. Is that the one you are referring to?
I really want to know how you can know that :D
@gimre: Nice, I didn't know that feature. Block explorer is becoming really nice!
You found the private key? Sorry, but I doubt that, so how did you do it?
Oh ok, I didnt get that you meant the 64 zeros are the private key for the multisig account, sorry.
Yes, funny, you are right 
And yes, doesnt help, because it is a multisig account and you can't send anything from there.
You have a multisig account in there .
TBONKWCOWBZYZB2I5JD3LSDBQVBYHB757VN3SKPP
It has a very simple private key. Is that the one you are referring to?
I really want to know how you can know that :D
@gimre: Nice, I didn't know that feature. Block explorer is becoming really nice!
Just tried different things and found it. It doesn't matter since it is a multisig account. Try using 64 zeros.
I don't think this is the account Gimre is talking about though.
YES, that's what the question was about :)
Congratulations, sir! much faster than expected :)
how did you find out "It has a very simple private key" ?
Its funny, cuz these 64 zeros was the only string from block 1 (besides all the recipient addresses of course) I didn't try to import as a private key {"hash": "ec188749598a6e573815a6226b778001066936ebd86569311c527045d872cbbf", "transactions":<br />[...], "timestamp": "2015-02-01 00:00:00", "prevBlockHash": {"data": "0000000000000000000000000000000000000000000000000000000000000000"}, "timestamp_unix": 1422748800.0, "txes":<br />[...], "height": 1, "version": 1, "signature": "ec188749598a6e573815a6226b778001066936ebd86569311c527045d872cbbf17846adbbe9e196578d07d7022fe837d8cf1be4d6b0d37461209a97777dc1904", "signer": "e59ef184a612d4c3c4d89b5950eb57262c69862b2f96e59c5043bf41765c482f", "type": -1, "timeStamp": 0}
I should have figured that out though, because there is no "prevBlockHash" for the nemesis block, so that kind of was the only thing (besides messages) where a private key could have been hidden.
well done jadedjack!
there is ONE MORE interesting account… and it's also been in nemesis block, who's gonna find it?
