Quote from: albert0bsd on Today at 12:05:41 PM

Quote from: AlanJohnson on Today at 11:51:33 AM

Now look into block explorer ... in 2023 there was a valid OUTGOING TRANSACTION from that address !!!

It is not an Outgoing transaction. An outgoing transaction is when that address is used as INPUT.

In the TX that you are mention:

Code:

b0780488cab40d45567a1eac97c2a456b48b216af3e6ecf47f1e5948a07e8c49

The address is bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn is listed as OUTPUT in the 2023 TX.

In the 2024 TX it was an INPUT.... Please learn something before talk

Quote from: AlanJohnson on Today at 11:51:33 AM

Compressed bech32 address derived from that key is : bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn

No the address was derived from the Legacy address

Code:

P2PKH: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
Hash: 20d45a6a762535700ce9e0b216e31994335db8a5

P2WPKH: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn
Hash: 001420d45a6a762535700ce9e0b216e31994335db8a5

As you see you only need the RMD160 hash of it 20d45a6a762535700ce9e0b216e31994335db8a5 just apend two bytes 0x00 and 0x14 before the original hash see? No public key was needed for that

OK. I admit i was wrong.

Now i see it was INCOMING tx TO that address. My bad.