The thing that actually matters: two kinds of confirmed
Base is an optimistic rollup. Transactions are executed and ordered by a sequencer, which produces a result in about two seconds. That result is what your wallet shows you and what BaseScan marks as confirmed.
It is not settled. Settlement happens when the sequencer posts a batch of transactions 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 and the distinction is academic. For a large transfer, for a withdrawal to Ethereum, or for anything where you are relying on irreversibility, the distinction is the entire question.
BaseScan's transaction page shows the L1 batch and its status. That is the field to look at, and it is the single reason to prefer BaseScan over a generic explorer that shows you the rollup state and stops.
| Stage | Typical 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. Reconstructable by anyone. |
| State root proposed | Hours | The claimed result is published on Ethereum. |
| Challenge window elapsed | Days | Final. Bridge withdrawals become claimable. |
Why your bridge withdrawal is taking a week
This is the most common Base support question and the answer is structural rather than a fault.
Moving assets from Ethereum to Base is quick — you deposit on L1 and the rollup credits you within minutes. Moving them back through the canonical bridge requires the challenge window to pass first, because until it does, the state you are claiming against could in principle still be disputed.
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 prove and finalise on Ethereum with a second transaction you have to actually submit. People routinely complete step one and assume they are finished.
BaseScan tracks the stages. Third-party bridges that offer instant withdrawals work by fronting you the funds on Ethereum and taking on the wait themselves, which is a legitimate service with a fee and a counterparty — a different risk, not an absence of one.
Everything else is Etherscan
Contract verification, the read and write tabs, proxy resolution, token transfer lists, the approval checker — all present, all behaving exactly as they do on Etherscan. If you know one, you know the other.
That consistency is worth something. 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.
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.
API access
Base is chain ID 8453 on the Etherscan V2 API, so it shares a key and a request shape with Ethereum, Arbitrum and Polygon. What it no longer shares is the free tier. We tested a free key against chain 8453 on 17 September 2026 and got back a flat refusal — Free API access is not supported for this chain. Please upgrade your api plan for full chain coverage — on every attempt. Base is a paid chain on the API now, whatever the website costs.
GET https://api.etherscan.io/v2/api
?chainid=8453&module=account&action=txlist
&address=0x...&apikey=YOUR_KEYIf you are on a paid plan, remember the per-second limit is shared across chains on one key rather than granted per chain: polling Ethereum and Base together gives you five calls per second between them, not five each.
If you are not on a paid plan, this is the point at which Base costs you something real, and it is worth knowing before you build. The practical answer is the same one that applies whenever a commercial API moves a chain behind a paywall — run the open-source alternative, or read the chain directly.
The open-source alternative is a Blockscout instance for Base, which gives you an Etherscan-compatible API from software you can read and run. On a chain this young that is a genuinely competitive option, and it is the one we would choose if the work were sensitive.
Which Base explorer should you use?
BaseScan for anything involving settlement, bridging or contract verification. The L1 view is the differentiator and nothing else presents it as clearly.
Blockscout if openness matters to you. It covers Base, it is auditable, and on a chain with a short history self-hosting is actually feasible rather than theoretical.
3xpl if you just want a fast lookup on a poor connection — it indexes Base and renders before BaseScan has loaded its assets.
Whichever you pick, internalise the finality point. It is the one thing about Base that will cost you if you get it wrong, and it is not the explorer's job to warn you.