MegaETH RPC Endpoint

Flat-rate MegaETH RPC provider and MegaETH RPC node access: free tier, no KYC, HTTP & WebSocket. MegaETH mainnet chain ID 4326.

MegaETH mainnet RPC URL: https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY
WebSocket: wss://rpc.swiftnodes.io/ws/megaeth?key=YOUR_API_KEY

Get your free MegaETH API key

250,000 requests/month · 20 req/s · all chains · no card · no KYC

Get my free API key →

MegaETH is an Ethereum layer 2 built for real-time execution, using ETH for gas. Its sequencer streams results in mini-blocks roughly every 10 ms and seals standard EVM blocks about once per second.

Network: MegaETH
Type: EVM
Chain ID: 4326
Slug: megaeth
Native token: ETH (Ether)
Block time: ~1.0 seconds (measured)
Finality: ~32 minutes to the finalized tag (measured)
Mainnet: February 2026
Category: Optimium (OP Stack L2)

MegaETH on the SwiftNodes fleet, right now

Status: online
Latency: 149 ms
Latest block: 32,545,094
WebSocket: available
Uptime, last 30 days: 99.99%

10 of 12 probed RPC methods supported (archive, batch, debug_traceCall, trace_transaction). The gaps are listed per chain in the method support matrix.

Status and latency from our health checks, refreshed about every 5 minutes. Uptime history. Method support probed automatically on 2026-11-01. Network status

MegaETH developer facts, measured

Block time:
~1 s (average of the last 1,000 blocks)
Finality:
the finalized tag trails the head by ~2,085 blocks (~35 min)
eth_getLogs range:
50,000-block ranges accepted (the largest we test)
Historical state:
readable at least 1,000,000 blocks back

Measured 2026-11-22 through this page's endpoint, re-measured weekly. Limits can differ between the upstream nodes behind it. All chains: measured chain facts.

About MegaETH

MegaETH's mainnet first went live in November 2025 and opened to the public in February 2026; the MEGA token launched on April 30, 2026. L2BEAT classifies it as an OP Stack optimium that uses EigenDA for data availability and a hybrid Kailua proof system, with a single centralized sequencer.

The chain is EVM-compatible, so existing Solidity contracts and tooling work. The key RPC difference is the Realtime API: reads such as eth_call, eth_getBalance and eth_getTransactionReceipt reflect the latest mini-block rather than the last EVM block, and eth_sendRawTransactionSync (EIP-7966) returns a receipt in the same call instead of requiring polling.

Common Use Cases on MegaETH

  • Low-latency trading and order books
  • Real-time onchain games
  • High-frequency DeFi
  • Apps needing immediate transaction receipts

MegaETH Mainnet RPC URL (HTTP)

https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY

MegaETH WebSocket RPC URL

wss://rpc.swiftnodes.io/ws/megaeth?key=YOUR_API_KEY

MegaETH Testnet RPC URL

Same API key, same plan: testnet requests count like any other request.

Testnet · chain ID 6343
HTTP: https://rpc.swiftnodes.io/rpc/megaeth-testnet?key=YOUR_API_KEY

Quick Start: Connect to MegaETH

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("MegaETH block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY"))
print("MegaETH block:", w3.eth.block_number)

Add MegaETH to MetaMask

Network Name: MegaETH (SwiftNodes)
RPC URL: https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEY
Chain ID: 4326
Currency Symbol: ETH
WebSocket: wss://rpc.swiftnodes.io/ws/megaeth?key=YOUR_API_KEY

Get your free MegaETH API key

30 seconds, no card, no KYC. Sign in with Google, GitHub, email or a wallet. Or try the requests above now with key=demo.

Get a free key →

Features of SwiftNodes for MegaETH

  • Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
  • Health-checked every 2 minutes with automatic failover
  • Free tier available — no credit card or KYC required
  • Flat-rate monthly pricing with no per-request fees
  • HTTP and WebSocket support
  • One API key works across all 139 supported chains and their testnets, including MegaETH

Rate Limits

PlanPriceHTTP req/sWS msg/sSign up
Free$0/mo201Start free →
Starter$49/mo7025Choose Starter →
Growth$89/mo15075Choose Growth →
Scale$149/mo300150Choose Scale →
Pro$249/mo600250Choose Pro →

Frequently Asked Questions: MegaETH

What is the MegaETH chain ID?

MegaETH mainnet uses chain ID 4326 (hex 0x10e6).

What is the difference between mini-blocks and EVM blocks on MegaETH?

The sequencer seals executed transactions into a mini-block about every 10 ms and streams receipts and logs to RPC nodes. About once per second it seals an EVM block containing those mini-blocks; standard block-based RPC methods refer to EVM blocks.

How do I get a transaction receipt without polling on MegaETH?

Use eth_sendRawTransactionSync (EIP-7966), which submits a signed transaction and returns its receipt in one call.

MegaETH RPC methods

Measured weekly through this endpoint: what each method returns on MegaETH, its limits, and an example request.

MegaETH guides from the blog

  • MegaETH RPC: A Developer's Guide (Chain ID 4326)MegaETH runs 1 s EVM blocks over ~10 ms mini-blocks. Measured: a 10-billion gas limit, transfers estimating 63,349 gas, a bogus eth_feeHistory oldestBlock, ~32 min to finalized, and what works over standard RPC.

Related L2 & rollup chains

Explore RPC endpoints for other L2 & rollup networks on SwiftNodes:

Ready to start building on MegaETH? Get a free API key in 30 seconds. No KYC, no card: sign in with Google, GitHub, email or a wallet.