Two addresses with same hash160? It seems that two addresses have same hash160 69665e2c4fac771e340f8c6f91c719b0c37a6a8f:


here 0 BTC: https://blockchain.info/address/1AcJanbHGrBFwS3KJMDW8kEZMtHiJhatzE
here 0.00720407 BTC: https://blockchain.info/address/3BJKWL5ipkVe2bjkRSt6ZNbVWQaRrEFjMs


How is this possible (it's probably not a collision, is it?)

Note: I first thought it would be because of compressed/uncompressed, but not possible: the ripemd160 hash is done after formatting the public key  (either to compressed or uncompressed) to hex, and after a SHA256 hash.
1AcJanbHGrBFwS3KJMDW8kEZMtHiJhatzE is a P2PKH (pay to pubkey hash) address. 3BJKWL5ipkVe2bjkRSt6ZNbVWQaRrEFjMs is a P2SH (pay to script hash) address. Their only difference is in the version byte that identifies the type of address.

However, in order to spend a P2PKH output, one needs to reveal the public key with the address's hash160. In order to spend a P2SH output, one needs to reveal the script with the address's hash160.

Given that the P2SH address has spending transactions already, clearly someone knows the script whose hash is 69665e2c4fac771e340f8c6f91c719b0c37a6a8f (namely the script 2 02707f8c41a9ce80bd85c335ce37617388fe8fd5c7b6079f730fc8b7159867cb3e 02f61a255027b492203f04396474e032e759367ad32cdb1b317074e216718f9b53 02ae11e6f80d33717c8dffcbd4e480b95f82f9fe7478cb166beebddd5b062c9f96 3 OP_CHECKMULTISIG, a 2-of-3 multisig script). It is astronomically unlikely that someone also has a public key whose hash is that some value (and much less knows the private key). As a result, it is extremely unlikely that funds sent to the P2PKH address are spendable.