bloXroute Documentation
WebsiteBlogTwitterDiscord
  • Welcome to bloXroute
  • Introduction
    • Why Use bloXroute?
    • Products
    • Create An Account
    • Technical Support
  • SOLANA
    • Trader API
      • Introduction
        • Regions
        • Authorization
        • Rate Limits
        • Tip and Tipping Addresses
      • Quick Start
        • Transaction Submission
        • Front-Running Protection & Transaction Bundle
        • Go SDK
        • Python SDK
        • Typescript SDK
        • Rust SDK
      • API Endpoints
        • Core Endpoints
          • submit
          • submit-paladin
          • submit-batch
          • balance
          • rate-limit
          • transaction
          • priority-fee
          • GetPriorityFeeStream
          • GetBundleTipStream
          • submit-snipe
        • Pump.fun
          • quotes
          • swap
          • swap-sol
          • GetPumpFunNewTokensStream
          • GetPumpFunSwapsStream
          • GetPumpFunAMMSwapsStream
        • Raydium
          • quotes
          • pools
          • pool-reserves
          • swap
          • cpmm-swap
          • clmm-swap
          • route-swap
          • GetPoolReservesStream
          • GetSwapsStream
          • GetNewRaydiumPoolsStream
          • GetNewRaydiumPoolsByTransactionStream
        • Jupiter
          • quotes
          • swap
          • swap-instructions
          • route-swap
        • Openbook
          • markets
          • orderbooks/{market}
          • depth/{market}
          • tickers/{market}
          • open-orders/{market}
          • unsettled/{market}
          • place
          • replace
          • cancel
          • settle
          • GetOrderbooksStream
          • GetTickersStream
      • Best Performance for Landing Transactions
      • Support
        • API Health
        • Contact us
        • Suggestions
        • Wiki
          • Terms & Concepts
          • Resources
    • Optimized Feed Relay (OFR)
      • Transaction Streamer
      • Gateway and OFR Requirements
      • Gateway and OFR Setup
      • Gateway Startup Arguments
      • OFR performance
      • Logging
      • Submitting Transaction
      • Upgrading Gateway
      • Troubleshooting
  • BSC & ETH
    • EVM Blockchain Distribution Network (BDN)
      • How to Connect
      • The bloXroute Gateway
        • Local Gateway
          • Installation and Startup
            • Authentication & Certificates
            • Requirements
            • Supported Clients
            • GitHub repository option
            • Docker container option
            • Startup Script
            • Startup Arguments
          • General Connectivity Troubleshooting
          • Logging
          • Upgrading your Gateway
        • Add Your Gateway as a Trusted Peer to Your Execution Layer Client
        • Connecting Your Gateway with the Consensus Layer
      • IPs & Relays
        • Relays IPs
        • Private Relays
        • Cloud-API IPs
          • ⏩Reducing Latencies using the BDN
    • APIs
      • Authorization
      • Check Transaction Quota
      • Submit a Transaction
        • Raw Transaction Construction
        • Tx-Validation
        • Batch Transaction
      • Private Transactions
        • ETH Private Transactions
        • BSC Private Transactions
      • Transaction Bundles
        • Bundle Simulation
        • Bundle Validation
        • Bundle Submission
          • BSC Bundle Submission
            • List of BSC Validators
          • ETH Bundle Submission
          • Bundle Submission with Gateway
        • Bundle Tracking
          • BSC Bundle-Trace
          • ETH Bundle-Trace
          • ETH Bundle Inclusion Status
        • Bundle Refunds
          • Priority Fee Refund
          • Bundle Refund
          • Latest Bundle Refunds
      • Backrun Arbitrage
        • BackRunMe: Bundle Submission
          • BSC submit arbOnly
          • ETH submit arbOnly
            • blxr_info
            • ETH arbOnly Simulation
      • Token Launch Sniping
      • Other Utilities
        • List of bloXroute Builders
        • List of External Builders
        • Tx-Trace
        • Ping
    • Streams
      • Requirements
      • Subscription limits
      • Working With Streams
        • Creating a Subscription
          • Websocket
          • gRPC
        • Handling the Notification
          • Websocket
          • gRPC
        • Cancelling a Subscription
          • Websocket
          • gRPC
        • Local Node Validation
      • newTxs and pendingTxs
        • Filters
        • Raw TX Reconstruction
      • BackRunMe: arbOnlyMEV
        • ETH arbOnlyMEV
        • BSC arbOnlyMEV
      • transactionStatus
      • txReceipts
      • newBlocks
      • bdnBlocks
      • ethOnBlock
      • MEVBlockValue
      • MEVNextProposerInfo
    • Block Builders and Validators
      • Validator Gateway
      • MEV Relay (For Validators)
      • Block Submission
      • Proposer MEV-Protect
      • Compliance Lists
      • Preconfirmations
    • Protect RPCs
      • ETH Protect RPC
      • ETH Gas Protect RPC
      • BSC Protect RPC
      • SOL Protect RPC
  • Base Network
    • Submit Transactions
    • Streams
      • GetBdnBlockStream
  • TON NETWORK
    • TON Trader API
      • Quick Start
      • Fee Schedule
      • Connection
      • Submit Signed Transaction
  • Resources
    • BDN Explorer
    • Block Explorer
    • Guides
      • Algorithmic Trading
      • Setting Up a Local Gateway
      • Gateway as Web3 Bridge
    • Architecture
      • BDN Architecture
        • Network Components
        • Performance Techniques
          • Block Compression
          • Cut-through Routing
          • Optimized Topology
      • bloXroute Protocol
        • Versioning
        • Message Structure
        • Message Types
    • Contact Us
Powered by GitBook
On this page
  • REQUEST
  • RESPONSE
  1. BSC & ETH
  2. APIs
  3. Transaction Bundles
  4. Bundle Tracking

BSC Bundle-Trace

The Bundle-Trace service allows traders to check the status of a submitted bundle - see if it has been included on-chain or the bundle exclusion reason.

The Bundle-Trace utility has a built-in rate limiting defined by the account tier.

Bundle-Trace returns the bundle hash and block number the bundle was sent to, together with the bundle's result.

REQUEST

curl \
    -X GET \
    -H "Content-Type: application/json" \
    -H "Authorization: <YOUR-AUTHORIZATION-HEADER>" \
    https://tools.bloxroute.com/bscbundletrace/<BUNDLE_HASH>
https://tools.bloxroute.com/bscbundletrace/<BUNDLE_HASH>?auth_header=<AUTH_HEADER>

parameters

Name
Description
Default

auth_header

Allows the user to include the authentication in the URL string directly.

If the authentication is provided in both the header and the URL parameter, the one in the header will be used.

None

block_number

Allows the user to specify the block number they sent the bundle to. In case the bundle was sent to multiple blocks - this parameter is mandatory

None

RESPONSE

Examples

Bundle is on chain:

{
    "bundleHash": "0x65a47c9648bf250aa79ee6ec1c5c2b5a18af49f4f22c1aba18a84f71875083fd",
    "blockNumber": 31104504,
    "result": "bundle is on chain"
}

Bundle failed - bundle was sent too late

{
    "bundleHash": "0x6bd0633961d11cc9ae5d3572fb24f3854f26f81189b6f67cb86721e1dfb59f35",
    "blockNumber": 31158286,
    "result": "builder did not include bundle in the block - bundle sent too late"
}

Potential Responses

Response
Description

bundle is on chain

The bundle is included in the on-chain block

bundle not found in our database. Bundle data might take up to 10 minutes to load.

The bundle hash is not found in our database. Bundle data becomes available in our database 10 minutes after the bundle submission, so If the bundle was sent recently you can try again later.

bloXroute bid did not win

The validator did not choose bloXroute's block.

bundle had an error on initial simulation - [error]

The bundle was not included in the block because it has an error not related to the other bundles and transactions. In case the bundle simulation fails when the bundle is the only bundle at the top of block, we consider it as an initial simulation error. Possible initial simulation errors are: sandwich / frontrun bundles, bundle reverted, transaction nonce too low

builder did not include bundle in the block - [reason]

The builder's winning block does not include this bunle. possible reasons: - bundle sent too late - bundle reverted or conflicted with other bundles/txs - a more efficient arrangement was found that does not include this bundle

Rate Limiting

Bundle-Trace is limiting requests if they exceed 2 requests per second. In addition, each tier has a limit to how many requests per day are allowed.

Below are the tiers limits:

Account Tier
Requests Per Day

Ultra

60

Enterprise-Elite

60

Enterprise

20

Professional

4

Introductory

4

PreviousBundle TrackingNextETH Bundle-Trace

Last updated 1 month ago