Solana Transaction Landing Benchmark

Cumulative ranking — across all measurements (on-chain confirmed)

Landing-slot distribution — share of each provider's landed txs by slots-after-send (mean first)

Recently verified on-chain — a sample of recent confirmed transactions, open any on Solscan

How we measure

Every number here comes from real mainnet transactions, each landing confirmed against the chain.

• Same transaction, raced. For each run we build identical transactions and fire them at every endpoint at the same instant. The only variable left is how fast each one gets the tx onto the chain.
• Shred-resolution landing detection. Instead of polling an RPC with "did it land yet?", we tap the validator Turbine stream directly and timestamp the moment the first shred carrying your transaction arrives. That's the earliest observable sign a block producer included the tx — single-shred precision instead of the hundreds-of-milliseconds blur of polling.
• Location-neutral latency. From the raw send-to-observe time we subtract network transit on both ends: a TCP-connect handshake to the endpoint on the way out, and the leader-to-our-node propagation on the way back. The reported milliseconds then reflect the provider's relay and inclusion speed, not how far our measurement box happens to sit. RPC processing time stays in the number, because that's the provider's job.
• Slot distance. Alongside milliseconds we report how many slots after send the tx landed. Slots are integer and identical for everyone on the network, so this number is immune to clock and distance effects and reads the same no matter where we measure from. We use shred arrival and slot distance rather than ticks on purpose: ticks are the usual unit for sub-block resolution, but they aren't tied to real time. They advance at each validator's own scheduler pace, so they aren't comparable across leaders.
• On-chain confirmed. We cross-check every landing against the chain: each tx's signature status and the slot it landed in. Latency percentiles shown are p50 / p95 / p99.

Measurement queue

Payment and execution status of recent measurement orders.

Request a measurement

Benchmark your endpoint(s) against the field. A run is queued once payment is confirmed on-chain — price is a small service fee plus the real transaction fees the run will incur.

My measurements

Enter your access token to see your orders and per-slot landing results.