[General] Unusually Long Transaction Creation Time (~30ms)

[kolesnevg]

Team or Project

No response

ZK chain

Era

Environment

Mainnet

L2 block number

No response

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

Hi team,

I noticed that creating the following transaction took approximately 30 milliseconds, which seems a bit longer than expected:

Tx hash: 0x23d98e85f74e5832e9c70a308790facdd48eaea938cd31c43e57730d59e89829

Is this an expected duration for transaction creation? Under typical conditions, I would expect this process to be significantly faster — usually in the sub-10ms range.

Additional context:

Running on Google Cloud, Debian 10

No unusual system load at the time

Using zksync2go

Let me know if there's any more information I can provide to help debug or verify this behavior.

Thanks!

Repo Link (Optional)

No response

Additional Details

No response

[sarahschwartz]

@kolesnevg yes I would say this is a standard time for transaction creation. Do you have any more context about why you expect a shorter time?

[kolesnevg]

Hi, thank you very much for your response!

I was developing bots that interacted with zkSync about a year ago, and back then the transaction submission latency was very low — I don’t remember exactly, but I think it was around 3–5ms. Now, sometimes it's 30ms, sometimes 50ms, or even higher. Could it be that there have been changes in how the zkSync sequencer works? I read somewhere that there were updates — and while it used to be centralized, it's now a distributed network of validators.

[RomanBrodetski]

Hey @kolesnevg thanks for reaching out!

So generally 30-50ms is very normal for transaction submission. Can you please specify what exact time are you measuring? API response time? Please note that it will take additional time (normally less than a second) to include the transaction into a block - so even if the response would be faster, it won't influence actual execution.

[kolesnevg]

Hi @RomanBrodetski, thank you for your attention!

For example, consider transaction 0x114d71b91a0077fe05e6e6ebc4cbdb44967eee3cdeaf612588d141918884c477:
An HTTP request to https://mainnet.era.zksync.io started at 2025-05-22T18:39:22.230677975Z and finished at 2025-05-22T18:39:22.401194034Z, with a duration of 171 ms.
However, the transaction appeared in the block at 2025-05-22T18:39:22.396661Z.
Is it normal for the API request itself to take this long?

[bxpana]

@kolesnevg Checked in with Roman and yes the latency is normal. The block timestamp is set when the block is open - so it's possible you submitted the tx even after the block was started (but before sealed). We are working on reducing this, but all in all the latency is to be expected.

[kolesnevg]

Thank you!