> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/transaction-submission/block-builder/overview.md). # Overview ### What is Block Builder? Block Builder is a BSC block building service provided by BlockRazor. It maintains competitive block building and high block production success rate based on [BEF](/core-technology/blockchain-edge-fabric.md) and Flow Coordination Engine. Block Builder currently ranks first in block production rate across the entire BSC chain. Real-time block production rate can be viewed at . Block Builder is designed for users who require high-quality BSC transaction execution. Its core value includes: * Higher win rate block building capability * Low-latency access capabilities for global deployment * Supports multiple transaction submission modes to adapt to different execution needs. * Provide more suitable submission paths for latency-sensitive, privacy-sensitive, and sequence-sensitive scenarios. ### Who is Block Builder suitable for? * **Searcher**: Users who need to submit bundles, capture MEV opportunities, and pay attention to the order of transactions and the timing of execution. * **Trading Bot / Quant Team**: Team with specific requirements for latency, execution stability, and cross-regional performance. * **Wallets / DEXs**: Teams that need a better trade execution experience, privacy protection, or a better submission path. ### What capabilities does Block Builder provide? Block Builder currently supports the following core capabilities: * **Send Bundle**: Suitable for scenarios that require transaction order, atomicity, and execution within the same block. * **Send PrivateTransaction**: Suitable for scenarios where you want to avoid exposing transactions to the public mempool and reduce the risk of being preempted or maliciously observed. * **Trace Bundle**: Suitable for scenarios that track and analyze Bundle submission results and execution performance. Combined with Bundle Explorer, it can help users observe the performance of Bundle in the Builder chain in a more granular way, providing a reference for strategy optimization, problem investigation and effect review. ### Endpoint **Default Access** Prioritize using a global, universal entry point, suitable for quickly completing integration and serving global requests. Endpoint: **** **Regional optimization** If your bot or service is already deployed in a specific region and is more sensitive to latency and consistency, you can further connect to a regional entry point on top of connecting to a globally universal endpoint.
RegionAvailable area（AWS）RPC Endpoint
Tokyoapne1-az4https://tokyo.builder.blockrazor.io
Frankfurteuc1-az2https://frankfurt.builder.blockrazor.io
Virginiause1-az4https://virginia.builder.blockrazor.io
Dublineuw1-az1https://dublin.builder.blockrazor.io
**Quality Enhancement** If you have already completed the basic integration and are starting to focus on the additional overhead in the commit path, cross-region fluctuations, and stability under high load, you can further integrate [Fast Submit](/transaction-submission/block-builder/fast-submit.md). ### Quick Start {% stepper %} {% step %} Apply for auth For details, see [Authentication](/get-started/authentication.md) {% endstep %} {% step %} Select the appropriate capabilities and endpoints based on the scenario and requirements. * [Send Bundle](/transaction-submission/block-builder/send-bundle.md) * [Send PrivateTransaction](/transaction-submission/block-builder/send-privatetransaction.md) * [Trace Bundle](/transaction-submission/block-builder/trace-bundle.md) * [Call Bundle](/transaction-submission/block-builder/call-bundle.md) {% endstep %} {% step %} Verify latency and stability performance in the real deployment area. {% endstep %} {% endstepper %} ### FAQ
What is the difference between submitting a Bundle to an RPC and submitting a Bundle to a Block Builder? The core difference between the two lies in the different submission paths and final destinations of the Bundle. When submitting a Bundle to BlockRazor RPC, BlockRazor RPC forwards the Bundle to mainstream builders with low latency. This approach is more suitable as a unified access point, allowing users to submit Bundles without having to connect to different builders individually. When you submit a Bundle to Block Builder, the Bundle is sent directly to BlockRazor Builder. This is more suitable for scenarios where you explicitly want to use BlockRazor Builder capabilities and the access path.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.blockrazor.io/transaction-submission/block-builder/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.