Hadal

A clearer view of Solana mainnet

See beyond
the send.

A transaction sent isn’t a transaction landed. Hadal follows what happens after it leaves the client, compares Solami Beam with plain RPC, and shows exactly what the evidence can and cannot say.

Open observatory Trace a real signature
  • Solami RPC
  • Beam HTTP + receipt
  • Yellowstone gRPC
Delivery pathsschematic
BeamPlain RPCgRPC streamsProcessed → Confirmed
Beam probeconfirmed

39BVXAWa…3tfignz

  1. Send0 ms
  2. Accepted154 ms
  3. First seen188 ms
  4. Confirmed342 ms
Slot 456,251,230 · one monotonic clock
Plain RPC probe
940ms to confirmed

first seen 700 ms · slot 456,251,331

n = 1 per routeintegration proof, not a ranking
mainnet-beta
  • Send
  • Transport accepted
  • Processed reception
  • Confirmed reception
  • Chain block time
  • Beam receipt

THE JOURNEY OF ONE TRANSACTION

Six moments.
Six different clocks.

Most tools collapse them into one number. Hadal keeps each moment, its source and its precision separate, so a contradiction is visible instead of averaged away.

  1. 01

    Send

    The collector stamps the call on a monotonic clock. Everything later is measured from this instant.

    Collector · monotonic
  2. 02

    Transport accepted

    The HTTP endpoint acknowledges. It can arrive after a stream already saw the transaction.

    Solami RPC / Beam · monotonic
  3. 03

    Processed reception

    A Yellowstone gRPC stream delivers the transaction. Reception time, not validator processing time.

    Yellowstone gRPC · monotonic
  4. 04

    Confirmed reception

    The confirmed stream reports it. Confirmed inclusion, not finality.

    Yellowstone gRPC · monotonic
  5. 05

    Chain block time

    The block records a time with one-second precision. Useful context, never a latency measurement.

    Solami RPC · 1 s precision
  6. 06

    Beam receipt

    A public routing record, when one exists. A missing receipt is unknown, not a failed delivery.

    Beam public lookup · its own clock

ONE OBSERVATORY. THREE PERSPECTIVES.

The full picture.
Without the guesswork.

For builders who care about what happens after their transaction leaves the client.

01

Two routes.
Side by side.

Beam and plain RPC, scored on the same workload, with the sample size always beside the number.

Explore route performance
02

Every attempt.
An open record.

A searchable, exportable ledger of recorded probes and where each timing came from.

Open the transaction ledger
03

One signature.
A deeper view.

Chain record, Beam receipt and collector observations, kept in separate lanes that can disagree.

Follow a transaction

READ THE LIMITS

  • Execution failure still proves inclusion
  • Pending is not a settled failure
  • Missing receipt means unknown
  • Slot leaders give context, not blame

WHAT TWO PROBES CAN SAY

2probes · 1 per route

Enough to prove the integrations work on mainnet. Not enough for a winner, a robust p95 or a speed claim, and Hadal says so on every screen.

RECORDED ON MAINNET · 13 OCT 2026

Real transactions.
Real clocks.

Two probes, one per route, sent about 20 seconds apart under a 110,000-lamport cap. No retries. Both confirmed without chain errors.

BEAMExecuted
342ms to confirmed reception
First seen
188 ms
Confirmed slot
456,251,230
Total cost
105,000 lamports
Beam receipt
Landed · ams
Open this trace
RPCExecuted
940ms to confirmed reception
First seen
700 ms
Confirmed slot
456,251,331
Total cost
5,000 lamports
Beam receipt
Not applicable
Open this trace

LESS GUESSING. MORE UNDERSTANDING.

Bring a signature.
We’ll follow the evidence.

Read-only from the first click. No wallet connection.