Base Benchmark: BlockRazor achieved a 67.75% inclusion win rate.
View Results
Sign in
Create Account

Multi-chain infrastructure comparison

Compare data delivery and transaction submission by chain.

BLOCKRAZOR vs. Jito Labs

Transaction submission

Jito Labs / Transaction submission
Jito LabsBlockRazorUser & business need examplesScope & integration differences
Execution bots: submit a time-sensitive single transaction
Compare direct engine submission with the selected BlockRazor route, Tip, privacy and fallback behavior.
Searchers, arbitrage teams: submit ordered transactions
Compare Bundle size, ordering, failure rules, Tips and status queries. Jito may also be a downstream engine of the submission service.

Official benchmarks

Benchmarks

Solana Shred Stream Benchmark vs Jito

Test period: August 2025 (Report date: )

Test content

Historical direct comparison of BlockRazor Shred Stream and the then-active Jito ShredStream. Teraswitch clients in Frankfurt, Amsterdam, New York and Tokyo captured both streams, matched Shreds by slot and index, and deduplicated them in one-minute windows to measure first arrival and arrival-time differences. This measures data delivery timing, not transaction execution or strategy outcomes.

Migration reference only. Jito ShredStream has retired. This report is not evidence for current Jito Block Engine performance or a promise about transaction submission.

Results

BlockRazor first-arriving Shreds (%)

Share of Shreds that arrived from BlockRazor first in each region. A higher percentage means more Shreds arrived from BlockRazor before Jito.

  • Frankfurt85.25%
  • Amsterdam61.40%
  • New York84.86%
  • Tokyo97.32%
How much earlier BlockRazor arrived than Jito (P50) (ms)

Jito arrival is the 0 ms reference. BlockRazor is to the left because it arrived earlier. Values show the median time difference, not total delivery latency.

  • FrankfurtBlockRazor earlier by 2.14 ms
  • AmsterdamBlockRazor earlier by 0.704 ms
  • New YorkBlockRazor earlier by 1.47 ms
  • TokyoBlockRazor earlier by 43.6 ms

A complete low-latency stack

01

See signals sooner

Receive blocks, mempool data, shreds, FlashBlocks, or sequencer updates earlier, giving your strategy more time to decide and act.

02

Improve transaction position

Use low-latency submission paths to improve your chance of earlier inclusion and a better onchain position when every block or slot matters.

03

Integrate with less effort

Connect through documented endpoints and familiar interfaces, with one team supporting both your data and transaction paths.

FAQ

Does overlapping service scope mean the providers or APIs are interchangeable?

Evaluate the scope within your workflow. Overlapping capabilities do not imply provider equivalence or drop-in API compatibility.

Choose the chain, signal, and submission path. Then test it in your region.

Explore the multi-chain catalog and pair receiving and sending services around your production constraints.