Discrepancy in Transaction of Batch Number on ZkSync Explorer - Etherscan Explorer.

[a1111198]

I encountered a discrepancy while checking a transaction in ZkSync Explorer for batch 488237. Here are the details:

• ZkSync Explorer Batch: Batch 488237
• Etherscan Transaction: Transaction on Etherscan

When I check the decoded input data for the transaction on Etherscan, it shows an input of batchNumber uint64 488236.

Discrepancy:

• ZkSync Explorer Batch Number: 488237
• Etherscan Decoded Input Batch Number: 488236
  
  

Where is this discrepancy coming from?

Reason for Inquiry:

I was trying to understand proto-danksharding from Patrick's video in the Foundry advanced course and encountered this issue. I want to know if this is a bug in the explorer or if there's a deeper concept that I need to understand.

Additional Context:

Any clarification on this matter would be greatly appreciated, as it will help me in understanding the workings of proto-danksharding and any potential impacts or issues in transaction processing.

Thank you!

[EngrPips]

I haven't seen that content myself, so I can't really be of help here, but I don't want to leave you hanging. Trust that @PatrickAlphaC or @ciaranightingale will attend to this as soon as they are available.

[PatrickAlphaC]

Good question... Let me check with zkSync.

[bxpana]

@a1111198 the 1. values on Etherscan are the for the previous batch, but if you scroll down you'll see the matching batch number under newBatchData

Glad to see more people learning about ZKsync and hope you're having a good time!

[EngrPips]

Interesting, Thanks for the heads-up, sir.

[bxpana]

My pleasure 😁