The hash160 of 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa is 62e907b15cbf27d5425399ebf6f0fb50ebb88f18, but I don't see any occurrences of it in pubkey script above (yes, I'm aware about endianness issues). How could Blockchain.info ever know that an output of that transaction is 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa?

1 Answer
1

This is a pay-to-pubkey (P2PK) script, where the transaction contains the destination public key itself. These were common in the early days of Bitcoin, and were originally the type of script that would be created by default by miners (see Why does the default miner implementation use pay-to-pubkey?), though nobody seems to know why this was chosen.

Nowadays the norm is to use a pay-to-pubkey-hash (P2PKH) script, which as you know contains the hash160 of the public key, rather than the key itself. You can note that such a script looks different, e.g.

Blockchain.info is taking the pubkey from the transaction, computing its hash, and converting it to a base58 address. This is just a convenience for the user, so that one can think of either P2PK or P2PKH transactions as crediting an "address". So Satoshi could use the same private key to spend a P2PKH transaction sent to the address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa, as to spend the genesis coinbase transaction (disregarding the fact that it actually can't be spent at all).