Block Timestamps

Block timestamps are the on-chain clock that vesting schedules, auctions, time-locks, and reward accrual read from block.timestamp, and off-chain indexers use to place OP Mainnet events in real time. On OP Mainnet (chain ID 10), with a new block roughly every two seconds, that clock ticks fast and smoothly — but it is set by the sequencer, not measured by a global consensus of validators, which changes how much you can trust it for fine-grained logic. This guide is for smart contract and backend developers who need to use OP Mainnet timestamps safely: it covers how they are assigned, what accuracy you can and cannot assume, the bounds on manipulation, network time drift, and the patterns that keep time-based logic robust.

Understanding Block Timestamps

• Who sets them: OP Mainnet has a single sequencer that produces blocks and assigns each block's Unix timestamp, generally advancing about 2 seconds per block in line with the block cadence. There is no PoW or multi-validator timestamp negotiation — the sequencer is the timekeeper, anchored to the OP Stack L1-derived block schedule.
• Accuracy guarantees: timestamps are monotonic (each block's timestamp is greater than its parent's) and track wall-clock time closely, but they are not a precise oracle. Treat them as accurate to roughly the block interval, not to the second or millisecond.
• Manipulation bounds: because the sequencer assigns timestamps, the manipulation surface differs from PoW chains, but you should still assume small adjustments are possible within protocol bounds. Never design logic that breaks if a timestamp is off by a few seconds, and never use block.timestamp as a randomness source.
• Network time drift: drift is the gap between a block's timestamp and true wall-clock time. On OP Mainnet it stays small thanks to the steady ~2s cadence, but it is non-zero — comparing OP Mainnet timestamps against your server clock or another chain's clock will reveal a few seconds of offset that you must tolerate.

Working with Timestamps

1// Get block timestamp
2const getBlockTimestamp = async (blockNumber) => {
3  const block = await web3.eth.getBlock(blockNumber);
4  return block.timestamp;
5};
6 
7// Calculate average block time
8const getAverageBlockTime = async (blockCount = 100) => {
9  const latestBlock = await web3.eth.getBlockNumber();
10  const oldBlock = await web3.eth.getBlock(latestBlock - blockCount);
11  const newBlock = await web3.eth.getBlock(latestBlock);
12 
13  return (newBlock.timestamp - oldBlock.timestamp) / blockCount;
14};

Best Practices

• Do not rely on exact precision: OP Mainnet timestamps are reliable to about the block interval, not the second. Design deadlines and windows so that being a few seconds early or late changes nothing material.
• Account for manipulation: in time-sensitive logic (auctions, vesting cliffs, time-locks), assume the timestamp could be nudged slightly within protocol bounds. Add tolerance margins so a small shift cannot trigger or block a critical state transition, and never derive randomness or pricing from block.timestamp alone.
• Prefer block numbers for ordering: to order events or measure elapsed intervals, use block numbers — they are strictly increasing and unambiguous. With ~2s blocks you can convert a target duration into an approximate block count when you need a clock-like measure that resists timestamp nudging.
• Handle drift in integrations: when correlating OP Mainnet timestamps with off-chain systems or another Superchain network, expect a few seconds of offset and reconcile against block numbers or a shared reference rather than assuming clocks match exactly.
• Safe time buffers: size buffers to comfortably exceed the block interval and any plausible drift — a buffer of at least tens of seconds (well above a single ~2s block) absorbs normal variation so legitimate transactions are never rejected for arriving a block early or late.

See also

• eth_getBlockByNumber - Retrieve block information including timestamps
• Working with Blocks - General block handling
• Block Gas Management - Managing gas costs over time