Conduit Explorer

Conduit Explorer is the default block explorer bundled with every Conduit chain. It’s available immediately when your chain launches—no setup, no waiting on indexing, and no extra infrastructure.

Pages load fast. Because Conduit Explorer reads directly from the chain’s RPC endpoint and skips the indexing layer that traditional explorers rely on, blocks, transactions, and contract data appear with minimal latency.

See it in action on Zora Mainnet.

Features

Search

The search bar appears on the home page and at the top of every page. It accepts:

• Addresses—opens the address page.
• Transaction hashes—opens the transaction receipt.
• Block numbers—opens the block detail page.

A keyboard shortcut focuses the search bar from anywhere in Conduit Explorer.

Blocks

Conduit Explorer paginates the block list and updates it live as new blocks arrive.

The block detail page shows block metadata, gas usage, and a paginated list of the transactions in the block with decoded descriptions.

A separate block countdown page estimates the time remaining until a future block.

Transactions

The transaction detail page uses tabs to surface the most important information up front:

• Overview—decoded description, value transferred, fee breakdown, gas usage, decoded calldata, and nonce.
• Balances—per-account balance changes for native value and token transfers.
• Calls—internal call list with decoded calldata, when the transaction has sub-calls.
• Events—event logs grouped by related events, with decoded parameters.
• Trace—full execution call tree and storage state diff, when supported by the chain’s RPC endpoint.
• Raw—the raw transaction and receipt data.

Transaction receipt

Every transaction has a dedicated receipt page designed for sharing and archiving:

• A clean, print-friendly HTML view with itemized fees, balance updates, and decoded events.
• A downloadable PDF rendering of the same view.
• A machine-readable plain-text or JSON response for terminal tools and scripts.

Addresses and contracts

The address page adapts to the type of account:

• Externally owned account—shows the native token balance and account information.
• Contract—adds a Contract tab (ABI, verified source code, and bytecode) and an Interact tab (read and write functions).

Conduit Explorer displays verified source code with syntax highlighting for Solidity, Vyper, and Rust. For contracts without verified source, Conduit Explorer automatically detects function and event signatures so calls and logs remain readable. See Verify contracts with Sourcify for instructions on verifying your own contracts.

Read-only contract calls work without connecting a wallet. To call write functions, connect an injected wallet such as MetaMask. Conduit Explorer estimates gas and shows real-time transaction status.

Conduit Explorer detects proxy contracts automatically and loads the implementation contract’s ABI for interaction.

User interface

• Live block number in the header that links to the latest block.
• Keyboard shortcuts for focusing search and switching between transaction and receipt views.
• Responsive layout for mobile and desktop.

When to use Conduit Explorer

Conduit Explorer is a good fit when you need a block explorer that’s:

• Available immediately with no setup or indexing wait time.
• Fast—pages load with low latency because data comes straight from RPC.
• Lightweight and low cost.
• Focused on inspecting individual blocks, transactions, and contracts.

When to use Blockscout or another provider

Indexing-backed explorer features are available as a paid add-on through Blockscout Hosted. Add Blockscout Hosted (or another indexed explorer) when you need:

• Full transaction history for an address.
• Token holder, transfer, and portfolio analytics.
• A public REST or GraphQL API for external integrations.
• ERC-721 and ERC-1155 token browsing.

Feature comparison

The following table compares Conduit Explorer to Blockscout in detail so you can decide whether you also need a Blockscout Hosted add-on for indexing-backed features such as address transaction history, token holder lists, or a public API.