Muhammet Kara: I didn't try it with a pending deploy yet but it seems that non-existent hashes are shown as "Unknown" and as an account hash -> that seems very confusing to me.

So yes, I think this is still relevant and could need some improvement because I've copied a deploy and modified 1 character only and it gets detected as an "Unknown account hash".

This is the original successful Deploy I've checked:

I've changed the last "f" to an "e" - not sure if that is a valid test though.

I did another test:

Testing it with a random wallet it is also just showing 0 balance -> I would expect a message like "Wallet doesn't exist. If it's your wallet make at least 1 transfer to this wallet to see the balance" or something like that because according to my knowledge a wallet which never received any CSPR doesn't exist yet.

Original random wallet:

I've changed the last "1" to a "2".

The "Named Keys" shows an error message for non-existing wallets btw. (see attached screenshot). So if this was done for security and/or against any kind of scraping protection - it failed.

Without testing on my side I would assume the same applies to some other hashes/urefs etc. as well.