0

There is some strange TX

9c7b0d0423af64e81c4b850bae781e41077586a9e3328f5048f8367c6e4a8212

that doubled in blockchain local database.

Blockchain.info information is truly interesting. Is it a scum or what is it?

enter image description here

3

Two different blocks were mined at height 494676, i.e. two different blocks both naming the same previous block as their parent. One of them has a hash starting 262f and the other is 6d0d. Both of them included the 9c7b transaction. This happens normally from time to time; for instance, it could be that 262f was mined first, but it wasn't relayed to the other miner fast enough, so they kept trying blocks with the previous parent and ended up mining 6d0d. Or it could be that they were coincidentally mined very close to the same time. The timestamp on 6d0d is 56 seconds later, but timestamps are not guaranteed to be accurate.

Only one of the two can be included into "the" eventual blockchain, so following this, miners creating new blocks had to make a decision as to which of the two to name as parent. 262f won, so 6d0d is now orphaned and is not part of the main blockchain; Bitcoin nodes won't consider it part of the authentic transaction ledger, and the miner who created it can't spend the block reward.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.