--- title: BlockRazor Ethereum RPC description: MEV-protected Ethereum Mainnet RPC for private transaction routing, inclusion, and eligible backrun rebates. canonical: https://blockrazor.io/rpc/ethereum/ language: en last-updated: 2026-10-23 --- # BlockRazor Ethereum RPC BlockRazor Ethereum RPC routes Ethereum transactions privately to reduce sandwich and frontrunning exposure, improve transaction inclusion, and return up to 90% of eligible backrun revenue under the current product rules. ## Network and endpoint - Network: Ethereum Mainnet - Chain ID: `1` - Public endpoint: `https://eth.blockrazor.xyz` - Project endpoint format: `https://eth.blockrazor.xyz/` Use the public endpoint for supported wallet and trader workflows. Projects that require identification, usage management, or dedicated configuration should use the endpoint assigned through the BlockRazor Portal. Never publish private RPC identifiers or credentials. ## Main capabilities - Private transaction routing intended to reduce public-mempool exposure - Protection against common sandwich and frontrunning paths - Transaction submission optimized for inclusion - Up to 90% of eligible backrun revenue returned under current rules - Standard JSON-RPC integration for wallets and applications Capabilities, eligibility, rate limits, methods, and routing behavior may change by service configuration. Confirm production requirements in the current documentation. ## Production metrics and methodology These metrics apply only to the BlockRazor Ethereum RPC service. Public and project-dedicated access are two access modes for the same RPC service. The figures cover production traffic across all global regions and exclude non-RPC submission channels. Monthly metrics are updated once per month; the latest monthly reporting period is September 2026. ### 98% next-block inclusion rate - Reported value: `98%` - Reporting period: September 2026 - Definition: transactions confirmed in the next block divided by all transactions that passed RPC validation and were accepted by the Ethereum RPC service - Measurement rule: when a transaction is sent, BlockRazor records the latest chain block number (`N`). After the transaction is confirmed on-chain, BlockRazor records its inclusion block number (`M`). The transaction counts as a next-block inclusion when `M - N = 1`. - Scope: Ethereum RPC production traffic across all global regions - Source: BlockRazor internal production telemetry - Verification status: First-party measurement; not independently audited ### $300,000 in cumulative rebates - Reported value: `$300,000` in USD-equivalent value - Measurement coverage: all available production records from the service's official launch through the end of September 2026 - Definition: cumulative rebates already paid to Ethereum RPC users in ETH, the network's native asset - Conversion method: each real-time rebate is converted to its USD-equivalent value using the native-asset price at the time the rebate occurs - Scope: Ethereum RPC production traffic across all global regions - Source: BlockRazor internal production telemetry - Verification status: First-party measurement; not independently audited ### 99.99% service availability - Reported value: `99.99%` - Measurement coverage: all available production records from the service's official launch through the end of September 2026 - Definition: percentage of time in which the monitored RPC method calls completed successfully across BlockRazor's global Ethereum RPC regions - Scope: the globally distributed Ethereum RPC production service - Interpretation: this is observed historical availability, not a prospective SLA guarantee - Source: BlockRazor internal production telemetry - Verification status: First-party measurement; not independently audited ### More than 200,000 daily successful on-chain transactions - Reported value: more than `200,000` transactions per day - Reporting period: September 2026 - Definition: transactions accepted by the Ethereum RPC service and subsequently confirmed on Ethereum Mainnet - Scope: Ethereum RPC production traffic across all global regions; non-RPC submission channels are excluded - Source: BlockRazor internal production telemetry - Verification status: First-party measurement; not independently audited ## Frequently asked questions ### How can transactions receive refunds while resisting MEV attacks? The project's transactions are shared with Searchers according to custom disclosure. Searchers can only perform harmless backrun strategies on transactions, thereby not only defending against sandwich and front-running attacks but also rebating the profits generated from backrun to users ### When and in what form will I receive the refund? If there is an opportunity to execute the backrun strategy in the transactions submitted by the project, the refund is completed by the Searcher calling the smart contract in real-time, meaning that the rebate transaction and the project transaction will be successfully executed within the same block ### Will the transactions be reverted? The default setting for the MEV Protect RPC is to disable revert protection for transactions. If you want revert protection for your transactions, use the /fullprivacy or /maxbackrun endpoint, or enable it in the portal. ### Can BlockRazor Ethereum RPC provide fast, MEV-protected private submission? BlockRazor Ethereum RPC privately routes Ethereum Mainnet transactions to reduce sandwich and frontrunning exposure, with the public endpoint at https://eth.blockrazor.xyz. Network conditions, transaction validity, fees and builder behavior still affect latency and inclusion, so production teams should validate current limits and tail latency with their own workload. ## Resources - Product page: https://blockrazor.io/rpc/ethereum/ - Ethereum RPC documentation: https://docs.blockrazor.io/transaction-submission/rpc/ethereum.md - Website resource index: https://blockrazor.io/llms.txt - Traditional Chinese resource index: https://blockrazor.io/zh/llms.txt - Documentation index: https://docs.blockrazor.io/llms.txt