Ethereum Stack Exchange is a question and answer site for users of Ethereum, the decentralized application platform and smart contract enabled blockchain. It only takes a minute to sign up.
Sign up to join this community
On web3.eth.subscribe('newBlockHeaders') I get notification and trying to get last block via saved block number earlier. It was happen with 9559839 block number on mainnet. First, I was get data with 197 transactions, a little bit later with 41 transactions (as it should be). And among these 41 transactions 33 was included in the block that I received earlier.
geth was launched on fast sync mode
This is quote normal situation, when several blocks with the same number are mined. Here is your block 41 transaction: https://etherscan.io/block/9559839, and here are two other blocks with the same number: (https://etherscan.io/uncle/0x42f5c5c14ffca28215cb3029f3f0d5b83cae3526b3da8bb9775a3ddd7b15c7a6 and https://etherscan.io/uncle/0x151331fd5bd238c6a1544703e8b9719ef85c2f01f00786b4a6aea954ac35d226). One of them is probably the block you saw with 197 transactions.
Different miners are working in parallel on the same block numbers. In case two or more miners manage to find block almost simultaneously, several blocks with the same number start spreading over the network. Each node decides by itself what block to trust and set further. This ambiguous situation remains until block with the next number is mined. In this next block only of only the competing previous blocks is referred as parent (this block becomes the "true" one whose transactions are actually persisted), and the other competing blocks become uncles and their transactions are effectively reverted. Here is the next block that refers one "true" parent and two uncles: https://etherscan.io/block/9559840
