Send raw transactions
You can send transactions through MEV Blocker either programmatically using its dedicated endpoints, or by updating your wallet's RPC URL.
Send raw transaction
Once your transaction is signed, submit it to your selected endpoint using the
eth_sendRawTransaction method.
eth_sendRawTransaction requires:
- A fully constructed Ethereum transaction.
- Local signing (by wallet, SDK, or custom solution).
- RLP-encoded transaction data: the raw, hex-encoded RLP string (for example,
0x02f8...).
- Example request
- Example response
curl -X POST https://rpc.mevblocker.io/fast \
-H "Content-Type: application/json" \
-d '{
"jsonrpc":"2.0",
"method":"eth_sendRawTransaction",
"params":["0xf869018203e882520894f17f52151ebef6c7334fad080c5704d77216b732881bc16d674ec80000801ba02da1c48b670996dcb1f447ef9ef00b33033c48a4fe938f420bec3e56bfd24071a062e0aa78a81bf0290afbc3a9d8e9a068e6d74caa66c5e0fa8a46deaae96b0833"],
"id":1
}'
{
"id": 1,
"jsonrpc": "2.0",
"result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
}
Choose your endpoint
MEV Blocker offers multiple endpoints, each optimized for different use cases. Choose the endpoint that best fits your needs:

Fast
- Fast:
https://rpc.mevblocker.io/fast—Fast inclusion with rebates. Transactions are simulated in a pending block.
fast gets transactions included onchain as quickly as possible while also finding users a rebate.
No reverts
- No revert:
https://rpc.mevblocker.io/noreverts—No revert guarantee. Transactions are simulated in a pending block.
noreverts gets transactions included onchain without any possibility of reverting.
If a transaction is no longer valid, it will stop being broadcast to builders at no extra cost to the user.
Full privacy
- Full privacy:
https://rpc.mevblocker.io/fullprivacy—Maximum privacy, no rebates. Transactions are simulated in a pending block.
fullprivacy gets transactions included onchain directly via a builder.
This method doesn't offer a rebate, but it guarantees that a user's transaction remains private.
Users should be aware that builders will still see their transaction information due to the architecture of PoS on Ethereum,
and can theoretically act maliciously.
In theory, however, they shouldn't, as there's no financial gain.
Max backruns
- Max backruns:
https://rpc.mevblocker.io/maxbackruns—Maximum backrun opportunities. Transactions are simulated in a pending block.
maxbackruns gets as many backruns for transactions as possible.
This endpoint shares all received transactions with searchers.
No checks
- No checks:
https://rpc.mevblocker.io/nochecks—Skip simulation checks. Transactions are NOT simulated in a pending block.
nochecks lets transactions go through even if the simulation fails.
Boost services
If you don't want to risk MEV Blocker downtime, you can leverage the Boost services which, in the event of MEV Blocker RPC being down, forwards traffic to Flashbots' RPC so that your transactions land onchain.
Fast boost
- Fast boost:
https://boost.rpc.mevblocker.io/fast—Fast endpoint with Flashbot fallback
No reverts boost
- No revert boost:
https://boost.rpc.mevblocker.io/noreverts—No revert endpoint with Flashbot fallback
Next steps
Consider following these next steps:
- Use one of the custom MEV Blocker RPC endpoint parameters.
- Wallet developers: Learn how to integrate MEV Blocker into your wallet product.