Bundle Trace
The Bundle-Trace service allows users to check the status of a submitted bundle — whether it was included on-chain, or how it behaved within bloXroute’s internal system.
It provides detailed insights including the bundle hash, block number, simulation results, and visibility across bloXroute and external builders.
Bundle-Trace limits requests to 1 request every 30 seconds and 4 requests per day.
Purchase the Bundle Trace Add-on to increase the limit to 60 requests per day for this endpoint.
Submission Endpoint
Method:
ethbundletraceEndpoint:
https://tools.bloxroute.com
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.
block_number
[Optional]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
Examples
Option 1 – curl Command :
curl -X GET \
-H "Content-Type: application/json" \
-H "Authorization: <YOUR-AUTHORIZATION-HEADER>" \
https://tools.bloxroute.com/ethbundletrace/<BUNDLE_HASH>Option 2 – URL with Query Param:
Response Fields
bundle_hash
Hash of the submitted bundle.
on_chain_status
Whether the bundle was included on-chain.
block_number
Block number the bundle was targeted for.
bloXroute
Internal trace details (see breakdown below).
bloXroute Field Breakdown
Receive time
Time when bloXroute first received the bundle.
Initial simulation
Outcome of the initial bundle simulation (e.g., success, nonce error).
Effective gas price
Measured gas price of the bundle.
First inclusion in bloXroute block
Timestamp of first inclusion in bloXroute-simulated blocks.
Inclusion %
Percentage of blocks where the bundle was included.
Rejection reason
Reason for non-inclusion in our block (e.g., higher-paying bundles).
Final simulation error %
Percentage of how many blocks the bundle had final simulation errors in.
Last updated