[General] batch numbers not matching up #629
-
EnvironmentMainnet Provide a brief description of the functionality you're trying to implement and the issue you are running into.A Cyfrin Updraft user saw this discrepency between explorerers. If you click on the Etherscan link in the ZKsync explorer link, the batch number is different. Why is that? Cyfrin/foundry-full-course-cu#1943 Repo Link (Optional)No response Additional DetailsNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
It appears you are encountering an issue with mismatching batch numbers between the ZKsync explorer and Etherscan. This discrepancy can occur because ZKsync operates on a Layer 2 (L2) network, while Etherscan tracks the Ethereum mainnet, a Layer 1 (L1) network. Batch numbers in ZKsync (L2) are not the same as block numbers on Ethereum (L1). For a deeper understanding of how batch and block numbers operate within the ZKsync network, you can refer to the ZKsync documentation on Blocks and Batches. If you need further clarification or assistance, please let me know! Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support. |
Beta Was this translation helpful? Give feedback.
-
|
Will check this out to see what's up. |
Beta Was this translation helpful? Give feedback.
-
|
@PatrickAlphaC the |
Beta Was this translation helpful? Give feedback.
@PatrickAlphaC the
1.values on Etherscan are the for the previous batch, but if you scroll down you'll see the matching batch number undernewBatchData