Two kinds of confirmed
Base is an optimistic rollup. Transactions are executed and ordered by a sequencer, producing a result in about two seconds. That result is what your wallet shows you and what the explorer marks as confirmed.
It is not settled. Settlement happens when the sequencer posts a batch to Ethereum, and full finality under the optimistic model arrives only after the challenge window — during which anyone may submit a fraud proof — has elapsed. That window is measured in days.
For buying a coffee, the two-second confirmation is what matters. For a large transfer, a withdrawal to Ethereum, or anything relying on irreversibility, the distinction is the entire question.
| Stage | Timing | What it means |
|---|---|---|
| Sequencer confirmation | ~2 seconds | Executed and ordered. Reversible if the sequencer misbehaves. |
| Batch posted to L1 | Minutes | Data is on Ethereum and reconstructable by anyone. |
| State root proposed | Hours | The claimed result is published on Ethereum. |
| Challenge window elapsed | Days | Final. Bridge withdrawals become claimable. |
The comparison worth knowing: a validity rollup such as Linea or Starknet proves correctness cryptographically and has no challenge window at all. Both kinds of chain use the word "confirmed"; only the field on the page tells you which guarantee you have.
The withdrawal that stalls at step one
Moving assets from Ethereum to Base is quick: deposit on L1 and the rollup credits you within minutes. Moving them back through the canonical bridge requires the challenge window to pass first.
So a canonical withdrawal is a three-step process spread over days. Initiate on Base. Wait for the state root and the challenge period. Then submit a second transaction on Ethereum to prove and finalise.
That final step is yours to make and it does not happen automatically. A surprising number of people complete step one, wait a week, and assume something has gone wrong — when in fact the funds are sitting claimable, waiting for a transaction nobody told them to send.
BaseScan tracks the stages, which is the only reliable way to distinguish "waiting normally" from "waiting for you".
Third-party bridges avoid the wait by giving you funds on Ethereum immediately from their own liquidity and absorbing the challenge period themselves. That is a legitimate service with a fee and a counterparty. The canonical bridge has no counterparty and a delay. Neither is wrong; they are different risks, and it is worth knowing which one you chose.
Everything else behaves like Ethereum
Contract verification, the read and write tabs, proxy resolution, token transfer lists and the approval checker all work exactly as they do on Ethereum. Base is EVM-equivalent and the explorer reflects that.
That consistency has real value. Base has attracted a lot of newcomers, and the fact that the explorer works identically to the one every tutorial uses removes a whole category of confusion.
One thing that does not carry across: token approvals are per-chain. Approvals you granted on Ethereum do not appear on Base and vice versa. Each chain needs checking separately, which people consistently forget, and it is exactly the sort of thing that matters only after a protocol is exploited.
Fees on Base are low enough that the gas tracker is close to decorative, particularly since EIP-4844 blob transactions reduced the cost of posting data to Ethereum. That is a compliment to the chain rather than a criticism of the explorer.
The case for the open-source option
Most of our chain pages note that Blockscout exists and then observe that self-hosting is impractical for an individual. On Base that is not true, and it is worth saying so.
Base launched in 2023. Its history is short, its state is small, and running an archive node for it is a fraction of the commitment that an Ethereum mainnet archive node represents. Blockscout against that node gives you an Etherscan-compatible API from software you can read.
For anyone whose lookups are sensitive, or who would simply rather verify than trust an index, that is a genuinely available option here in a way it is not on older chains. Our self-hosting guide covers what it actually takes.
For everyone else, BaseScan is the default and there is no strong reason to fight that — with the single proviso that the L1 batch field is the one worth learning, and nothing on the page tells you why.
Practical notes for Base users
Base is easy to use and has a few specific traps worth knowing about.
Addresses are identical to Ethereum. The same address works on both, which is convenient and means a transaction sent to the right address on the wrong chain is a real possibility. Contracts, however, are not identical — a contract deployed on Ethereum does not exist on Base at the same address unless someone deliberately deployed it there.
Token approvals are per-chain. Approvals granted on Ethereum do not appear on Base and vice versa. Each chain needs checking separately, and people consistently forget the newer one.
Bridged tokens are not the original. A token bridged to Base is a separate contract issued by the bridge. It represents the original and it is not the original, and there can be several bridged versions of the same asset from different bridges. Always verify the contract address against the project's own documentation rather than trusting a name.
Sequencer dependency. Base currently has a single sequencer. If it goes down, the chain stops producing blocks until it recovers or the escape-hatch mechanisms are used. This is a known property of most rollups today rather than a Base-specific flaw, and it is worth understanding before assuming a rollup has the same availability guarantees as Ethereum itself.
None of these is a reason to avoid the chain. They are the things an explorer will not warn you about, which is why they are written down here.