I created a parser and cut up the complete chain into items.
When inserting them right into a database, to my shock there have been 187 blocks with the identical hashes, so initially I assumed there was one thing unsuitable with what I used to be doing, however after debugging, I discovered duplicates contained in the blockchain.
I solely investigated one block with the hash: 00000000000000000002927103A1BC8426DEFE05CFFA40BE468072B984C8876B.
I discovered the identical block in two completely different .dat information: blk03361.dat, blk03363.dat.
I do know for positive that the 2 blocks are similar as a result of I cut up each dat information into blocks and in contrast the hashes:
sha256sum 1/1_part_65.bin
d81340e3e1c1759e4b78dc1cd531230b55d1828fd14ed0f9ba8cd9269a7ee322 1/1_part_65.bin
sha256sum 3/3_part_77.bin
d81340e3e1c1759e4b78dc1cd531230b55d1828fd14ed0f9ba8cd9269a7ee322 3/3_part_77.bin
The primary one has the peak 772553 and the second 772776.
Is that this regular?
I created a parser and cut up the complete chain into items.
When inserting them right into a database, to my shock there have been 187 blocks with the identical hashes, so initially I assumed there was one thing unsuitable with what I used to be doing, however after debugging, I discovered duplicates contained in the blockchain.
I solely investigated one block with the hash: 00000000000000000002927103A1BC8426DEFE05CFFA40BE468072B984C8876B.
I discovered the identical block in two completely different .dat information: blk03361.dat, blk03363.dat.
I do know for positive that the 2 blocks are similar as a result of I cut up each dat information into blocks and in contrast the hashes:
sha256sum 1/1_part_65.bin
d81340e3e1c1759e4b78dc1cd531230b55d1828fd14ed0f9ba8cd9269a7ee322 1/1_part_65.bin
sha256sum 3/3_part_77.bin
d81340e3e1c1759e4b78dc1cd531230b55d1828fd14ed0f9ba8cd9269a7ee322 3/3_part_77.bin
The primary one has the peak 772553 and the second 772776.
Is that this regular?
