Monad Atlas

HTTP JSON-RPC

Standard EVM JSON-RPC over HTTPS. Compatible with ethers.js, web3.js, viem.

Endpoint

URL https://api.monadatlas.com/rpc

All requests require an API key. See Auth.

Supported Methods

Standard EVM methods including:

  • eth_blockNumber — Current block
  • eth_getBlockByNumber — Block by number (with full tx objects)
  • eth_getBlockByHash — Block by hash
  • eth_getTransactionByHash — Transaction details
  • eth_getTransactionReceipt — Receipt with logs
  • eth_getLogs — Historical logs (fromBlock, toBlock, address, topics)
  • eth_call — Contract read
  • eth_estimateGas — Gas estimation
  • eth_sendRawTransaction — Submit signed tx

Example

curl -X POST https://api.monadatlas.com/rpc \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_KEY" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

eth_getLogs (historical events)

The upstream Monad node limits the block range per request (typically 100–1000 blocks). Use chunked queries for large ranges.

{
  "jsonrpc": "2.0",
  "method": "eth_getLogs",
  "params": [{
    "fromBlock": "0x3a1c000",
    "toBlock": "0x3a1c063",
    "topics": ["0xddf252ad..."]  // Transfer(address,address,uint256)
  }],
  "id": 1
}

Block range limit: Keep toBlock - fromBlock ≤ 100 blocks for compatibility. Chunk larger ranges (e.g. 10,000 blocks → 100 requests of 100 blocks each). Error block range too large means the range exceeds the node limit.

Real-Time Subscriptions

For eth_subscribe (newHeads, logs, monadLogs, pending), use the WebSocket endpoint. monadLogs delivers events from proposed blocks for lower latency. See WebSocket.