bloXroute

• Name: bloXroute
• URL: https://bloxroute.com/
• Category: transaction-delivery / mempool-data / MEV infrastructure
• Summary: bloXroute is a low-latency transaction-delivery and mempool-visibility vendor built around its Blockchain Distribution Network (BDN). The useful analytical cut is that bloXroute sells privileged position inside the time-sensitive path between orderflow, data visibility, and block inclusion rather than merely offering generic node infrastructure.
• What it does:
  • Operates the Blockchain Distribution Network (BDN), which bloXroute describes as a globally distributed, high-capacity relay network optimized for low-latency propagation of blockchain transactions and blocks
  • Sells execution services for transaction submission, bundle submission, and chain-specific trading / execution APIs intended for professional traders, searchers, validators, and infrastructure teams
  • Sells data services including real-time blockchain streams and Optimized Feed Relay (OFR) products for systems that need fresher signals for execution or analytics
  • Supports multiple chains in current docs, including Solana, BNB Chain, Base, Ethereum, X Layer, Hyperliquid, Monad, and TON
  • Maintains public gateway and chain-client repositories that show the practical operator-facing surface behind the marketing site
• Key claims:
  • The homepage says users can “see swaps, blocks, and mempool activity in real time” and “submit transactions and bundles with the lowest latency and highest reliability”
  • The docs describe bloXroute as providing “a high-performance networking layer for blockchain transactions and data” and say it reduces latency and variance via the BDN
  • The docs split the product into execution services and data services, both backed by the same BDN infrastructure
  • The docs say bloXroute is used by “professional traders, searchers, and validators” across several production chains
  • The public gateway repo describes the gateway as a blockchain client that attaches to nodes and serves as an entrypoint to the BDN, which helps anchor bloXroute’s networking claims in an actual operator product
• Whitepaper: An official whitepaper is linked from bloXroute’s public gateway README and was saved locally as ../whitepapers/bloxroute-whitepaper-v1.1.pdf. Current operational understanding in this pass came more from the official site, docs, and GitHub materials; see ../whitepapers/bloxroute-primary-sources-2026-04-26.md.
• Sources:
  • https://bloxroute.com/
  • https://docs.bloxroute.com/
  • https://docs.bloxroute.com/introduction/readme.md?ask=What%20products%20or%20surfaces%20does%20bloXroute%20provide%20and%20who%20are%20they%20for%3F
  • https://docs.bloxroute.com/introduction/readme.md?ask=How%20does%20bloXroute%20describe%20its%20Blockchain%20Distribution%20Network%20and%20its%20execution%20and%20data%20services%3F
  • https://github.com/bloXroute-Labs
  • https://raw.githubusercontent.com/bloXroute-Labs/gateway/master/README.md

Internal linkages

• Closest execution-supply-chain peer on Ethereum: flashbots
• Solana-side comparison for private-orderflow and validator-adjacent routing: jito
• Useful relay-market context for proposer / builder separation: mev-boost

Control surface

• Power sits in gateway access, feed quality, relay placement, validator and searcher relationships, and who gets the fastest path into the BDN.

• This is private routing and data-distribution infrastructure. Transactions still settle on the destination chain, but the timing edge and visibility edge live inside bloXroute’s operator network.

• Once a trading or search stack is tuned around that network edge, the service stops looking like commodity node plumbing and starts acting like a rent-bearing chokepoint.

• Last reviewed: 2026-06-01 UTC