Overview
Bundle Tracing gives searchers and integrators full visibility into the lifecycle of every bundle submitted to Eureka Builder — from receipt through simulation to on-chain inclusion. All tracing data is queryable via JSON-RPC after submission.
How It Works
When a bundle is received, the builder records a timestamped event and assigns it a
bundleHash.As the bundle progresses through simulation and block building, additional events are appended to its timeline.
If the builder wins the slot and includes the bundle, the final status is set to
included.If the target block passes without inclusion, the bundle is marked
expired.All events and metadata are queryable for approximately 7 days after submission.
Use Cases
Inclusion tracking — confirm whether your bundle was simulated, included, or dropped, and why
Refund verification — look up the on-chain payout transaction for bundles with
refundPercentBlock analysis — inspect all bundles that targeted a specific block and the final block composition
Transaction lookup — find which bundle(s) a given transaction was part of
Orderflow attribution — understand whether a bundle originated via MEV Blocker, Servo, or direct submission
Data Retention
Bundle data is retained for approximately 7 days (configurable per deployment).
Authentication
Most endpoints are public. Some may require an accessToken for private metadata — see individual endpoint docs.
Rate Limits
All bundle tracing endpoints are rate-limited to 50 requests per second. Contact the Eureka team to request higher limits.
API Methods
Get inclusion stats and timeline for a submitted bundle
Get refund and payout info for a bundle
List all bundles that targeted a given block
Look up bundles containing a specific transaction
Get orderflow source metadata for a bundle
All requests are sent as JSON-RPC 2.0 POST to:
Last updated
