Dedicated Ethereum RPC

Dedicated Ethereum nodes. Full history, no limits.

Your own Ethereum full or archive node with every namespace you need: debug, trace, txpool and the Beacon API. No compute-unit math, and no block-range caps on eth_getLogs.

Why dedicated

Stop paying per trace.

Shared providers meter the most useful Ethereum methods hardest. On your own node, archive queries and traces cost the same as everything else: nothing extra.

Shared RPC plans

  • ✕eth_getLogs capped to small block ranges
  • ✕debug_ and trace_ methods locked to premium tiers
  • ✕Archive queries billed at multiples of a normal call
  • ✕Throttling during busy blocks and popular mints

DexOpticon dedicated

  • ✓Pull logs across any block range the node can serve
  • ✓debug_traceTransaction, trace_block and the rest, included
  • ✓Historical state at any block for one flat price
  • ✓Consistent performance with no neighbours

Capabilities

Built for indexers, searchers and serious dApps.

Full or archive

Choose a full node for current state, or an archive node for historical state at every block since genesis.

Debug & trace APIs

debug_traceTransaction, debug_traceCall and the trace_* namespace enabled for analytics, simulation and MEV research.

Your choice of client

Geth, Nethermind, Erigon or Reth on the execution side, paired with Lighthouse, Prysm, Teku or Nimbus. We'll recommend the best fit.

Mempool access

The txpool namespace and newPendingTransactions subscriptions, straight from your own node's mempool.

Beacon API included

Consensus-layer access for staking dashboards, validator tooling and recent blob data, from the same deployment.

Mainnet & testnets

Production on mainnet, with dedicated Sepolia and Hoodi nodes for staging.

What you get

Your Ethereum node, spelled out.

NetworkEthereum mainnet (Sepolia and Hoodi available)
Node typesFull or archive
EndpointsHTTPS JSON-RPC, WSS subscriptions, Beacon API
Namespaceseth, net, web3, debug, trace, txpool
ClientsGeth, Nethermind, Erigon or Reth + Lighthouse, Prysm, Teku or Nimbus
LimitsNone. No compute units, no block-range caps
PricingOne flat monthly price, quoted for your workload

FAQ

Questions, answered.

What's the difference between a full node and an archive node?

A full node keeps the current state and recent history, which is enough for most dApps, wallets and bots. An archive node also keeps historical state at every block, which you need to query balances or contract storage at past blocks, or to trace old transactions.

Which Ethereum client should I run?

It depends on the workload. Reth and Erigon are the most storage-efficient for archive nodes and heavy tracing, and Geth is the most widely used for full nodes. We'll recommend a client pairing when we quote.

Can I run eth_getLogs over large block ranges?

Yes. We don't impose block-range or result caps. Very large ranges are limited only by how quickly the node can scan them, and we can size the hardware for log-heavy indexing.

Do I get access to the mempool?

Yes. Your node's own mempool is available through the txpool namespace and newPendingTransactions WebSocket subscriptions.

How long does it take to get an Ethereum node?

A full node using snapshot or checkpoint sync is typically ready within about a day. Archive nodes take longer, depending on the client. We'll give you a concrete timeline with your quote.

Do you support Ethereum testnets?

Yes. Dedicated Sepolia and Hoodi nodes are available, on their own or alongside mainnet.

Get a node

Tell us what you're building.

Share a few details and we'll come back with a hardware spec, timeline, and flat monthly quote, usually within one business day.

  • No commitment to request a quote
  • Talk directly with an engineer
  • Any chain, any region

Prefer email? hello@dexopticon.io