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>
parameters
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
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:
Ultra
60
Enterprise-Elite
60
Enterprise
20
Professional
4
Introductory
4
Last updated