BSC Public Mempool
This section introduces the services, advantages, application scenarios, and access methods of BlockRazor BSC Public Mempool.
What is BSC Public Mempool
Public Mempool is a high-performance pending transaction stream based on BEF, used for low-latency subscription to unconfirmed transactions in public propagation.
In the EVM network, transactions typically propagate through the mempool before entering a block. The core value of the Public Mempool is to help users obtain publicly available pending transaction signals earlier and integrate these signals into their strategy systems with lower latency. It is commonly used to monitor public trading activity, track Smart Money behavior, identify new opportunities, and provide faster signal input for strategies such as backrun, copy trading, and sniping. For systems that rely on pending signals to drive trading decisions, seeing transactions earlier often means:
Entering the strategy judgment process earlier
More time to complete calculations and risk control
Higher probability of obtaining a better execution position in competitive scenarios
Scenarios of BSC Public Mempool
Pending Transaction Monitoring: Real-time monitoring of publicly distributed pending transactions to identify active addresses, popular contracts, or unusual transaction behavior.
Smart Money Tracking: Track transaction activity at target addresses early on, providing signals for copy trading or strategy following.
Backrun Discovery: Identifying publicly trades that may trigger backrun opportunities, allowing more time for subsequent strategy evaluation and trade submission.
Sniping Opportunities: Capture the first signals in the open market as early as possible when new pools launch, liquidity injections occur, or target trades emerge.
Real-time data input for strategies: Serving as a real-time input source for the trading system, it can be used in conjunction with capabilities such as Block Stream, Node Stream, RPC, or Block Builder to build a more complete monitoring and execution project.
Benchmark
In our transaction reception latency benchmark, we compared BlockRazor with a regular Node in four regions: Dublin, Frankfurt, Tokyo, and Virginia. The evaluation was based on the time difference for clients receiving the same transaction from BlockRazor and regular Node among comparable samples.
Dublin
99.7%
43.7 ms
28.8 ms
89.7 ms
Frankfurt
99.5%
29.0 ms
21.5 ms
48.1 ms
Tokyo
99.8%
136.4 ms
119.5 ms
218.7 ms
Virginia
99.8%
55.1 ms
40.5 ms
107.4 ms
The results show that BlockRazor maintained a significant lead in all four regions. Its transaction reception lead rate exceeded 99% in all regions. In terms of lead magnitude, BlockRazor's average lead time in different regions was approximately 43.7ms, 29.0ms, 136.4ms, and 55.1ms; under the P90 dimension, the lead magnitudes reached 89.7ms, 48.1ms, 218.7ms, and 107.4ms, respectively.
The results above demonstrate that BlockRazor exhibits a stable priority reception capability in the transaction propagation chain, enabling it to capture transactions earlier than ordinary nodes in the vast majority of comparable samples.
Price
Endpoint
Frankfurt
64.130.47.75:50051
Tokyo
63.254.162.18:50051
Dublin
141.98.217.82:50051
Virginia
208.91.105.204:50051
Request Parameters
NodeValidation
Mandatory
boolean
false
This field currently only supports being set to false, and the relay will push all new transactions (unchecked) with lower latency.
Request Example
https://github.com/BlockRazorinc/relay_example
Proto
The code of relay.proto is as follows:
Response Example
Success
Error
Last updated
Was this helpful?