Bitcoin Address is a public key and the balance is a public matter, it is not a big deal for anyone to find out the balance on a BTC address.
The Bitcoin address is not a direct public key but an encoded representation of the hash of the public key*.
Uh yeah, it turns out that this difference is very significant, because in terms of security, you could attack bare public keys with a quantum computer, but the same cannot be said for an address hash because of the extra SHA-256 step.
Sure, quantum computers don't exist in a commercial form right now, but there is nothing stopping it from being created in the future.
Yeah, a Bitcoin address will be more difficult to attack than a public key because the address has gone through the extra SHA-256 step, as in the P2PKH address example I mentioned earlier.
- Execute SHA256 on PubKey
- Execute RIPEMD160 on hash_sha256_PubKey
- Execute SHA256 on hash_01
- Execute SHA 256 on hash_02
- Execute Base58 encode on hash_final
By the way, I just tried checking the old type of BTC address (P2PK)* used on the genesis transaction:
04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f
using Google, but Google couldn't track it.
In this case, using Google to check the balance of Bitcoin assets is not optimal compared to using the Bitcoin Blockchain Explorer.
https://mempool.space/address/04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f*
A P2PK does not have an official address. However, you'll sometimes find blockchain explorers displaying addresses for P2PK locking scripts, even though they technically do not have one.