How to Submit a Transaction to Private Mempool
Learn how to submit transaction to private mempool directly to block builders, protecting you from MEV extraction until it's included in a block.
When you submit a transaction to the public mempool, it's visible to everyone. MEV bots can:
Sandwich your trade: Place orders before and after yours to extract value
Front-run you: Copy your trade and execute it first
Back-run you: Profit from the price impact you create
Meanwhile, Private transactions eliminate this exposure by hiding your transactions until they are included.

Private TX vs Public Mempool
Visibility
Everyone sees it
Only builders see it
MEV exposure
Vulnerable
Protected
Inclusion speed
Gas price dependent
Builder dependent
Best for
Speed-competitive scenarios
Value-sensitive trades
When to Use Private Transactions
Use private transactions when:
Executing large swaps that could be sandwiched
Trading tokens with low liquidity
Running strategies you don't want copied
Protecting any transaction from front-running
Request Sample
transaction
string
Yes
Signed raw transaction hex
mev_builders
array
No
Builders to send to. Default: ["all"]
How to Submit Transaction to Private Mempool
Set up the project
Set the ES module "type": "module" in your package.json.
Create a file and name it index.js
Create .env file and add the following:
Import the dependencies
Create and Sign Your Transaction
Submit Privately
Response
Selecting Specific Builders
There are list of builders who should receive the transaction without delay. There are:
bloxroute: bloXroute internal builder(default)all: all buildersOther options:
48club,blockrazor,jetbldr,nodereal
Troubleshooting
Transaction not included
Without a priority tip, private transactions compete based on gas fees alone. If your transaction isn't being included:
Increase gas price — Higher gas = higher priority for builders
Add a priority tip — See Private Transactions with Tips
Try specific builders — Some builders may be more responsive
"Invalid transaction"
Verify your transaction is properly signed
Check the chain ID is
56(BSC Mainnet)Ensure the nonce is correct
Connection issues
Verify your API key is valid
Check network connectivity
Try reconnecting after a few seconds
Next Steps
To increase the priority for inclusion in your private transactions, see Private Transactions with Tips.
Last updated
Was this helpful?