Public Mempool
Receive publicly propagating pending transactions over gRPC before ordinary node feeds in most comparable samples.
Low-latency streams and transaction paths for bots, searchers, wallets, DEXs, and infrastructure teams.
Combine early pending data, confirmed blocks, synchronized node state, and faster public transaction propagation.
Receive publicly propagating pending transactions over gRPC before ordinary node feeds in most comparable samples.
Consume the latest block header, confirmed transactions, and next-validator information through a regional stream.
Connect your own BSC full node to BlockRazor relays for earlier block and world-state synchronization.
Send single or batched public transactions without adding a tip to the transaction itself.
A like-for-like benchmark compares BlockRazor and bloXroute across Node Stream, Block Stream, mempool monitoring, and public transaction submission in four matched regions.
Read the BlockRazor vs bloXroute benchmarkUse the signal, state, and submission layers independently or combine them in one latency-sensitive workflow.
Public Mempool and NewBlocks
Fresh local node state
Broadcast Tx or BSC RPC
Use Public Mempool for pending signals, NewBlocks for confirmation data, and Full Node Synchronization when the strategy needs fresher local state. Complete the path with Broadcast Tx for public propagation or BSC RPC and Builder products when private or builder-aligned execution is required.
Connect your own BSC full node to the nearest BlockRazor Full Node Synchronization relay so it can receive blocks and update world state earlier. If the application only needs block signals rather than complete local state, use NewBlocks instead, and validate both first-arrival and state-ready time from the production region.
No. Broadcast Tx enters public propagation and focuses on lower-latency sending without an added tip. Use BlockRazor BSC RPC or another private path when MEV protection is required.
NewBlocks pushes structured block data to an application. Full Node Synchronization connects your own BSC full node to BlockRazor relays so the node can update blocks and world state earlier.
Current documentation lists Dublin, Frankfurt, Tokyo, and Virginia. Choose the endpoint closest to the application or node deployment and validate it against your production traffic.
Tell us about your partnership goals or subscription questions. Our business team can help with subscription plans, pricing, and ways to work together.
Log in to get your auth token and start building. You can contact us on Discord during integration.