Warning
This project is under active development and not yet suitable for production. For questions or feature requests, contact us on Telegram or submit an issue. To track progress, star the repository. Supported by an Optimism grant, the project is divided into four milestones. This warning will be removed after completion of Milestone 4.
- Milestone 1: Homepage and basic nav (current stage)
- Milestone 2: Tx detail page
- Milestone 3: Contract detail page
- Milestone 4: Feedback incorporation and polish
OP Scan is a transaction explorer tailored specifically for the OP Stack and the Superchain vision. It's focused on being lightweight so that anyone can run it locally next to an OP Stack devnet or any other compatible OP Stack based rollup.
- Lightweight: The code and dependencies are designed to be minimalistic. This ensures minimal resource consumption, allowing anyone to run it locally alongside an OP Stack node when working on a rollup.
- OP Stack Native: This explorer is purpose-built for the OP Stack. It ensures 100% compatibility with rollups in Optimism’s Superchain.
- Scalable: Despite its lightweight design, the explorer is built to handle any scale.
- Open Source: All code is open source from day one. This alignment with the community allows anyone to contribute or fork the repository to meet their specific needs.
OP Scan is built for rollups built on the OP Stack. If you are interested in it, have feedback or feature request, submit an issue here.
Here's a video walkthrough on how to launch the explorer locally configured for OP Sepolia testnet.
The app requires the following dependencies:
NodeJS >= 22
pnpm >= 9
Clone this repository:
git clone git@github.com:walnuthq/op-scanInstall the dependencies:
pnpm installYou will need to copy .env.local.example into .env.local at the root of your repository and populate it with your own values.
In particular you will need to provide configuration for both L1 and L2 chains:
NEXT_PUBLIC_L1_CHAIN_ID="11155111"
NEXT_PUBLIC_L1_NAME="Sepolia"
NEXT_PUBLIC_L1_RPC_URL="https://ethereum-sepolia-rpc.publicnode.com"
NEXT_PUBLIC_L2_CHAIN_ID="11155420"
NEXT_PUBLIC_L2_NAME="OP Sepolia"
NEXT_PUBLIC_L2_RPC_URL="https://optimism-sepolia-rpc.publicnode.com"
You can get free node rpcs url by signing up to services such as Alchemy, Infura or QuickNode.
You will also need to provide your L1 contracts addresses when using a devnet:
NEXT_PUBLIC_OPTIMISM_PORTAL_ADDRESS="..."
NEXT_PUBLIC_L1_CROSS_DOMAIN_MESSENGER_ADDRESS="..."
You will find theses addresses in your rollup deployment artifacts in contracts-bedrock/deployments/your-deployment/L1Contract.json.
Note that you always need to provide the proxy address, not the underlying contract.
If you don't want to run the explorer with your local chain setup, you will find all the necessary environment variables in .env.local.example to configure the explorer with OP Sepolia or OP Mainnet.
If you want to be able to use the Write Contract feature on verified contracts, you will also need to provide a Reown project ID.
NEXT_PUBLIC_REOWN_PROJECT_ID="REOWN_PROJECT_ID"
To run the indexer, you first need to setup your DATABASE_URL in .env.local (we use SQLite by default but you can switch to PostgreSQL by changing the Prisma provider in prisma/schema.prisma) as well as websocket connections to your L1/L2 chains:
DATABASE_URL="file:dev.db"
L1_RPC_WS="wss://ethereum-sepolia-rpc.publicnode.com"
L2_RPC_WS="wss://optimism-sepolia-rpc.publicnode.com"
Then you can sync your local database with the Prisma schema:
pnpm prisma:db:pushNow you will be able to start indexing the blockchain by running the op-indexer command:
pnpm op-indexerYou should start seeing blocks getting indexed in your terminal and you can explore the state of your local database using Prisma studio:
pnpm prisma:studioIf you need to change the Prisma schema at some point, make sure to regenerate the Prisma client and push to your local database:
pnpm prisma:generate
pnpm prisma:db:pushIndexing a blockchain is putting a heavy load on the RPC as you need to perform a large number of JSON-RPC requests to fully index a block (along with transactions and logs). When indexing non-local chains you will probably encounter 429 errors related to rate-limiting, you may provide up to 5 fallback RPC URLs in case this happens:
NEXT_PUBLIC_L1_FALLBACK1_RPC_URL="https://rpc.ankr.com/eth_sepolia"
NEXT_PUBLIC_L2_FALLBACK1_RPC_URL="https://rpc.ankr.com/optimism_sepolia"
NEXT_PUBLIC_L1_FALLBACK2_RPC_URL="https://endpoints.omniatech.io/v1/eth/sepolia/public"
NEXT_PUBLIC_L2_FALLBACK2_RPC_URL="https://endpoints.omniatech.io/v1/op/sepolia/public"
NEXT_PUBLIC_L1_FALLBACK3_RPC_URL="https://sepolia.drpc.org"
NEXT_PUBLIC_L2_FALLBACK3_RPC_URL="https://optimism-sepolia.drpc.org"
NEXT_PUBLIC_L1_FALLBACK4_RPC_URL="https://eth-sepolia.g.alchemy.com/v2/FALLBACK4_API_KEY"
NEXT_PUBLIC_L2_FALLBACK4_RPC_URL="https://opt-sepolia.g.alchemy.com/v2/FALLBACK4_API_KEY"
NEXT_PUBLIC_L1_FALLBACK5_RPC_URL="https://sepolia.infura.io/v3/FALLBACK5_API_KEY"
NEXT_PUBLIC_L2_FALLBACK5_RPC_URL="https://optimism-sepolia.infura.io/v3/FALLBACK5_API_KEY"
You can pass several parameters to the indexer to control the indexing range and execution:
--l2-from-block(short-f, defaults to latest block) start indexing from this L2 block.--l2-index-block(short-b) index this particular L2 block number.--l1-from-block(defaults to latest block) start indexing from this L1 block.--l1-index-blockindex this particular L1 block number.--index-delay(short-d, defaults to 1000) delay in ms between indexing 2 blocks to avoid overloading the RPC.
Example of running the indexer:
pnpm op-indexer -f 123416717 --l1-index-block 20426733 --l1-index-block 20426726 -d 500When you're done configuring your environment variables you can build the app:
pnpm buildMake sure your local chain is started and the indexer is running, then launch the explorer to see it live at http://localhost:3000
pnpm startAlternatively you can launch the explorer in dev mode if you want to customize it:
pnpm devHead on to the issues tab to find a list of open contributions. Before making your first contribution, get familiar with our contributor guidelines.