Links

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
browser
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.
validator chose local block over bloXroute MEV block
The validator did not choose bloXroute's block.
validator is not working with bloXroute
The validator for this block is not working with bloXroute to accept MEV bundles.
builder did not include bundle because of a permanent error - [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 a permanent error. Possible permanent errors are: mev gas price too low, bundle reverted, transaction gas price too low, transaction nonce too low
builder did not include bundle in the block - bundle did not pay enough
The bundle is paying less than other bundles and therefore is not included in the block
builder did not include bundle in the block - bundle was reverted or conflicted with other bundles/txs
The bundle was reverted or conflicted with another bundle or transaction in the same block.
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