Flashbots · Measurement guide
How to measure Flashbots transaction workflows
A practical template for separating simulation, relay response, on-chain inclusion, and transaction costs in your own test environment.
Linkable summary
Scope of this page
This page provides a measurement method, not FRB or provider benchmark results, an inclusion-rate estimate, or a relay service.
A repeatable test process
Use the same inputs and record each stage separately when comparing a configured workflow.
- Record the setup. Note network, endpoint, route, software versions, fee policy, region, and time window.
- Separate simulation from submission. Save simulation output and relay response as distinct events, including errors and timestamps.
- Check the chain outcome. Record target block, transaction status, confirmation, retries, and any replacement or cancellation.
- Report the sample and limits. Include sample size, exclusions, costs, raw evidence, and what the test cannot establish.
What to record
| Stage | Record | Interpretation limit |
|---|---|---|
| Simulation | Input, block context, result, and errors | A simulation is not a relay response or an inclusion result. |
| Submission response | Endpoint, route, timestamp, response or rejection | Acceptance by an endpoint does not guarantee a builder will include it. |
| On-chain outcome | Target block, transaction status, and confirmation | Report inclusion separately from submission and simulation. |
| Costs | Gas, priority fee, failed attempts, and conversion basis | Do not infer savings or profitability from route choice alone. |
Important limits
Relay acceptance does not guarantee builder selection or on-chain inclusion.
A private submission route does not guarantee privacy, protection, ordering, or profitability.
A single run cannot establish a stable rate, provider ranking, or general performance trend.
Primary references
Check current Flashbots documentation for route semantics and requirements.
Frequently asked questions
Does FRB guarantee a Flashbots inclusion rate?
No. Inclusion depends on the provider route, builder behavior, fees, competition, transaction validity, and network conditions. Measure your own sample.
Does a relay acknowledgement mean the transaction was included?
No. Record relay response and on-chain inclusion separately.
Does this page contain live FRB benchmarks or dashboard data?
No. It is a measurement guide; it does not provide a live data feed or comparative results.
Measure endpoint timing separately
The WSS test records client-observed endpoint timing and does not measure relay acceptance or transaction inclusion.
Open WSS latency test