MegaETH RPC Endpoint
Flat-rate MegaETH RPC provider and MegaETH RPC node access: free tier, no KYC, HTTP & WebSocket. MegaETH mainnet chain ID 4326.
https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEYwss://rpc.swiftnodes.io/ws/megaeth?key=YOUR_API_KEYMegaETH 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.
megaethMegaETH on the SwiftNodes fleet, right now
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-10-11. 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 ~1,883 blocks (~31 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-10-11 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_KEYMegaETH WebSocket RPC URL
wss://rpc.swiftnodes.io/ws/megaeth?key=YOUR_API_KEYQuick 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
https://rpc.swiftnodes.io/rpc/megaeth?key=YOUR_API_KEYwss://rpc.swiftnodes.io/ws/megaeth?key=YOUR_API_KEYFeatures 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 75+ supported chains, including MegaETH
Rate Limits
| Plan | Price | HTTP req/s | WS msg/s |
|---|---|---|---|
| Free | $0/mo | 2 | 1 |
| Starter | $49/mo | 50 | 25 |
| Growth | $89/mo | 150 | 75 |
| Scale | $149/mo | 300 | 150 |
| Pro | $249/mo | 500 | 250 |
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.
- eth_blockNumbersupported
- eth_chainIdsupported
- eth_getBalancesupported
- eth_getBlockByNumbersupported
- eth_getTransactionByHashsupported
- eth_getTransactionReceiptsupported
- eth_callsupported
- eth_estimateGassupported
- eth_gasPricesupported
- eth_maxPriorityFeePerGassupported
- eth_sendRawTransactionsupported
- eth_getTransactionCountsupported
- eth_getCodesupported
- eth_subscribesupported
- eth_getLogssupported
- eth_getBlockReceiptssupported
- eth_feeHistorysupported
- eth_getProofnot available
- eth_createAccessListsupported
- debug_traceCallsupported
- trace_blocksupported
- trace_transactionsupported
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? Connect your wallet and get a free API key in 30 seconds. No email or KYC required.