For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Region
BlockRazor Lead Rate
Avg Lead
P90 Lead

Dublin

84.0%

102.4 ms

221.0 ms

Frankfurt

99.7%

30.4 ms

67.7 ms

Tokyo

99.9%

148.6 ms

264.4 ms

Virginia

99.7%

62.0 ms

190.7 ms

The results show that BlockRazor maintained a significant lead in all four regions. Its transaction reception lead rate exceeded 99% in Frankfurt, Tokyo, and Virginia, while its lead rate in Dublin was 84.0%. In terms of lead magnitude, BlockRazor's average lead time in different regions was approximately 102.4ms, 30.4ms, 148.6ms, and 62.0ms; under the P90 dimension, the lead magnitudes reached 221.0ms, 67.7ms, 264.4ms, and 190.7ms, 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.

Endpoint

Region
Availability Zone(AWS)
Relay Address

Frankfurt

euc1-az2

35.157.64.49:50051

Tokyo

apne1-az4

54.249.93.63:50051

Ireland

euw1-az1

3.248.65.151:50051

Virginia

use1-az4

52.205.173.134:50051

Rate Limit

The price is $300 per data stream per month. Please go to the Pricing page to purchase.

The number of data streams that can be subscribed to is calculated on a shared basis across all regions. For example, if you purchase one stream, you can only subscribe in one region; you will not be able to subscribe in other regions.

Request Parameters

Parameters
Mandatory
Format
Example
Description

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?