Katana | Network Information — Chain ID, RPC, Gas & Explorer
Katana network information: Chain ID 747474, ETH gas token, public RPCs, block timing, EIP-1559 configuration, data availability and bridge references.
Mainnet parameters
Katana is an EVM-compatible Ethereum Layer 2. The mainnet Chain ID is 747474 and ETH is used as the gas token.
| Parameter | Value |
|---|---|
| Chain name | Katana |
| Chain ID | 747474 |
| Gas token | ETH |
| Block time | ~1 second |
| Gas model | EIP-1559 |
| Data availability | EIP-4844 |
RPC access
Katana has an official public RPC and an alternative public RPC route. Public endpoints can be rate limited, so production applications should use resilient provider configuration, retries and ideally more than one RPC source.
Explorer and bridge
Katana has a dedicated block explorer and canonical bridge infrastructure. Applications should link users to transaction and contract pages using the Katana explorer rather than assuming Ethereum explorers can interpret Katana state.
Gas and transaction behavior
Transactions pay gas in ETH. Applications should estimate gas dynamically, handle EIP-1559 fee fields and avoid hard-coding gas prices. Network capacity and gas conditions can change.
Account abstraction and predeploys
Katana supports modern EVM features including EIP-7702. Some OP Stack predeploys are available, but productive assets such as WETH may use Katana-specific implementations, so token addresses must be verified against the technical reference.
Production checklist
Verify chain ID, RPC health, gas token, explorer base URL, bridge route, token addresses and contract deployment before enabling transactions. Treat incorrect network configuration as a funds-safety issue, not just a UI bug.
Frequently Asked Questions
What is the Katana Chain ID?
Katana mainnet uses Chain ID 747474.
What token pays gas?
ETH is the gas token on Katana.
Is Katana EVM compatible?
Yes. Katana supports standard EVM development and wallet tooling.
Should production apps use a single public RPC?
No. Production systems should use resilient provider configuration and handle rate limits or endpoint failures.