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.
curl
browser
curl \
-X GET \
-H "Content-Type: application/json" \
-H "Authorization: <YOUR-AUTHORIZATION-HEADER>" \
https://tools.bloxroute.com/bundletrace/<BUNDLE_HASH>
https://tools.bloxroute.com/bundletrace/<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 |
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"
}
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 |
Last modified 2d ago