Quote from: AlanJohnson on Today at 07:14:26 AM

Quote from: benjaniah on Today at 06:53:24 AM

Quote from: Marcel. on September 20, 2024, 05:50:15 PM

priv2addr.py 2832ed74f2b5e35ee
Uncompressed Bitcoin Address: 138XxHZGcKM6WyWuYCijLsoCd8K3x4WYjs

Compressed Bitcoin Address: 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so

Uncompressed P2SH Address: 3GsgtYu5N1zZUAvtwwnN1sf9tf7shrJrex

Compressed P2SH Address: 3LPuXLDK7AGtmHLv5x1Aj7jSzKmD2Dj4Zr

Uncompressed Bech32 Address: bc1qzawsqu2pgrm7tglggkywujgfgefa56nwnlj6z3

Compressed Bech32 Address: bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn <-------

looks like someone done some transaction tests a day before moving the balance from 66..

https://talkimg.com/images/2024/09/21/gzrwW.jpeg

Hm, so someone sent 6001 satoshis to 'bc1qyr2956nky56hqr8fuzepdccejse4mw994lyftn' almost a year ago (Sept 18 2023)? I think it's safe to say, that whoever sent that 6001 satoshis knew 66's private key. What do you all think?

Something very fishy is going on here ... Shocked

Sending a transaction doesn't require knowledge of the private key. Anyone can initiate one, so it doesn't provide any meaningful information. I'm not sure what you're trying to get at with your suspicions.

hpsk

Posts

Merits