Chain profile

ZKsync Era chain ID 324, RPC URL, and explorer

Source snapshot

Source evidence snapshot July 4, 2026. ZKsync Era mainnet uses chain ID 324 / 0x144, RPC URL https://mainnet.era.zksync.io, explorer https://explorer.zksync.io, and ETH as the gas token. Use this page to copy the fields, open source evidence, and check setup cautions before use.

Quick settings

zkSync Era chain ID answer

ZKsync Era mainnet uses chain ID 324 / 0x144, RPC URL https://mainnet.era.zksync.io, explorer https://explorer.zksync.io, and ETH as the gas token. Copy the fields below and verify them against the linked source docs before using them in a wallet, script, or app.

Chain ID
324 / 0x144
RPC URL
https://mainnet.era.zksync.io
Explorer
https://explorer.zksync.io
Gas token
ETH
Source docs
ZKsync docs
Latest check
Jul 20, 2026
Source snapshot
July 4, 2026
Config path
wallet_addEthereumChain JSON

Copy ZKsync Era configOpen ZKsync Era guideExplorer directoryGas token directory

Good fit when you need:
  • the ZKsync Era chain ID, RPC URL, explorer, and gas token in one place;
  • source documentation links beside the copied setup fields;
  • manual wallet config fields without connecting a wallet or choosing an RPC provider.
Before you paste these fields:
  • compare the chain ID against the source link on this page;
  • open the explorer once and confirm it matches the network you expect;
  • use the public RPC for setup checks, then choose monitored infrastructure for production traffic.

Exact setup guide

ZKsync Era chain ID and RPC guide

Open this guide when you specifically need chain ID, RPC URL, explorer, gas token, or wallet configfor ZKsync Era. It keeps the copied fields, official/source docs, and setup cautions together in one focused reference.

Open ZKsync Era chain ID and RPC guideChain ID listMainnet RPC list

Chain ID324 / 0x144
RPC URLhttps://mainnet.era.zksync.io
Explorerhttps://explorer.zksync.io
Gas tokenETH
VerificationVerified metadata
Source snapshotJuly 4, 2026
Evidence snapshot

Verification record

Automated source snapshots and recorded probe evidence are tracked separately. The source snapshot timestamp is not a manual review date. This is not a live uptime, latency, or production reliability monitor. If a recorded public RPC probe fails, verify the source links and current endpoint availability before changing production configuration.

Automated source snapshot
Verification status
Verified metadata
Source snapshot run
source-monitoring-2026-07-04
Source snapshot tool
source-monitoring-refresh
Source set
ZKsync docs
Latest recorded chain ID probe
eth_chainId matched expected 0x144; observed 0x144 on

MethodologyReport a correction

ZKsync Era wallet-add fields

Wallet directory sites often expose a connect button. Main.net keeps the same MetaMask and EIP-3085 setup fields as text so developers can compare them with official/source docs before calling wallet_addEthereumChain.

chainId
0x144 (324)
chainName
ZKsync Era
nativeCurrency
ETH; name ETH, symbol ETH, decimals 18
rpcUrls
https://mainnet.era.zksync.io
blockExplorerUrls
https://explorer.zksync.io

Monitoring evidence

These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims. A source fetch failure or eth_chainId failure can mean a source page or public RPC endpoint was unavailable, changed, or rate-limited during a check. Re-open source links and test current RPC availability before relying on a public endpoint.

Snapshot generated
Source checks
1 sources checked
Source changes
0 changes since the previous source hash snapshot
Source fetch failures
0
eth_chainId probe
matched expected 0x144
Per-source check timing
Included in the monitoring snapshot, not represented as a manual review or page freshness date

View monitoring snapshots orsource change history.

Network endpoints

Primary public RPC
https://mainnet.era.zksync.io
Explorer
https://explorer.zksync.io
Official/source documentation
ZKsync docs
Chain type
ZK rollup L2 mainnet
Chain ID hex
0x144
Source snapshot provenance
source-monitoring-2026-07-04 via source-monitoring-refresh

ZKsync Era common questions

What is the ZKsync Era mainnet RPC URL?
ZKsync Era's listed primary public RPC URL is https://mainnet.era.zksync.io.
What is ZKsync Era's chain ID?
ZKsync Era's listed chain ID is 324.
What block explorer does ZKsync Era use?
ZKsync Era's listed block explorer is https://explorer.zksync.io.
What gas token does ZKsync Era use?
ZKsync Era's listed gas token is ETH.

Copy-ready config

Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.

Chain ID decimal324
Chain ID hex0x144
RPC URLhttps://mainnet.era.zksync.io
Explorer URLhttps://explorer.zksync.io
EIP-3085-shaped JSON

Rendered as text for manual review before use.

{
  "chainId": "0x144",
  "chainName": "ZKsync Era",
  "nativeCurrency": {
    "name": "ETH",
    "symbol": "ETH",
    "decimals": 18
  },
  "rpcUrls": [
    "https://mainnet.era.zksync.io"
  ],
  "blockExplorerUrls": [
    "https://explorer.zksync.io"
  ]
}

Developer snippets

Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.

ts

viem chain definition

Read-only snippet generated from Main.net fields. Review official sources before production use.

import { defineChain } from 'viem'

export const zksyncEraMainnet = defineChain({
  id: 324,
  name: "ZKsync Era",
  nativeCurrency: {
    name: "ETH",
    symbol: "ETH",
    decimals: 18,
  },
  rpcUrls: {
    default: { http: ["https://mainnet.era.zksync.io"] },
    public: { http: ["https://mainnet.era.zksync.io"] },
  },
  blockExplorers: {
    default: {
      name: "explorer.zksync.io",
      url: "https://explorer.zksync.io",
    },
  },
})
ts

wagmi read-only config

Read-only transport example generated from Main.net fields. It does not include account adapters or transaction actions.

import { createConfig, http } from 'wagmi'
import { zksyncEraMainnet } from './zksync-era'

export const config = createConfig({
  chains: [zksyncEraMainnet],
  transports: {
    [zksyncEraMainnet.id]: http("https://mainnet.era.zksync.io"),
  },
})
ts

ethers read-only provider

Read-only JsonRpcProvider example generated from Main.net fields. It does not create a signer.

import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider("https://mainnet.era.zksync.io", {
  chainId: 324,
  name: "zksync-era",
})

const network = await provider.getNetwork()
console.log(network.chainId)
bash

curl eth_chainId check

Minimal JSON-RPC identity check. This verifies the endpoint-reported chain ID only, not uptime or production suitability.

curl -s -X POST \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
  https://mainnet.era.zksync.io

# Expected chain ID: 324 / 0x144

Developer signals

External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.

Safety note

ZK rollups can have different tooling, finality, and withdrawal assumptions. Verify network details in ZKsync docs before deployment.

Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.

Report a correction

If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.

Report ZKsync Era dataSend page feedback