Bridge activity, read live
Feel the bridge
breathe into Solana.
Spanpulse watches the Solana-side core bridge and turns its raw signatures into a living heartbeat — a throughput pulse, message counts per hour and window, success versus error, and the live market header for the bridge token. Every on-chain read is real and keyless. Nothing here is bridged, traded, custodied or signed.
Read-only concept. This is the Solana-side core-bridge message rate over a recent sample of signatures — a pulse, not total bridged volume. Signatures and balances are live from the chain; the token price is live from DexScreener. The chain-to-chain flow map is a clearly-labelled concept layer. Not financial advice.
Your wallet
You, at the bridgehead
A read-only view of your connected wallet, read live from the chain through the same same-origin RPC the pulse uses. Spanpulse never requests a transaction or a signature — it only reads public on-chain data.
The heartbeat
Throughput pulse
Recent core-bridge signatures on Solana, bucketed into ten-minute bins across the sample window. Each bar is the real count of bridge messages that landed in that slice of time — a live heartbeat built directly from the chain. Hover a bar for its slice.
Reading recent bridge signatures from the chain…
Message counts are live, derived from getSignaturesForAddress on the core-bridge program over the most recent sample of signatures. This is a message-rate pulse, not a measure of USD value bridged. If the RPC is briefly busy the pulse reloads on its own; it is never faked.
The readout
Live bridge readout
The pulse condensed into numbers — messages in the last hour and across the full sample window, the success-versus-error split, the message rate, and the live market header for the bridge token W. Every tile here is a real read; none is modelled.
Hour and window counts, the rate and the success split are computed live from on-chain signatures. The W price, liquidity and 24-hour volume are live from DexScreener. Spanpulse holds no funds, routes nothing and is not affiliated with any bridge. Not financial advice.
Concept layer
Cross-chain flow map SAMPLE
A stylised picture of where bridge traffic could be arriving from. Per-chain origin data is not available from the keyless, same-origin hosts Spanpulse is allowed to call, so the split below is a modelled concept layer — the arc animation and the Solana-side pulse driving it are real; the per-chain weights are illustrative.
The per-chain flow weights are a clearly-labelled sample — not a live measurement. They are scaled by the live Solana-side message pulse so the picture breathes with real throughput, but Spanpulse cannot see which chain each message originated on from its allowed hosts, and does not pretend to.
Under the hood
How the pulse is built
Four steps, each a real call to a keyless endpoint. The only modelled part — the per-chain flow map — is labelled everywhere it appears.
-
01
Read the bridge
Spanpulse asks the chain, over a same-origin read-only RPC, for the core-bridge program's most recent signatures — up to five hundred of them.
…
-
02
Bucket the beats
Each signature carries a block time. We bin them into ten-minute slices to draw the throughput heartbeat and read off the window span.
…
-
03
Count & grade
We count messages in the last hour and the full window, derive a per-minute rate, and split landed messages from reverted ones using each signature's error flag.
…
-
04
Add the market
DexScreener gives the live price, liquidity and volume for the bridge token W. The cross-chain flow map on top is a clearly-labelled concept layer.
…
Straight answers
Questions
Is the pulse real on-chain data?
Yes. The heartbeat, the hour and window counts, the rate and the success/error split all come live from the core-bridge program's signatures, read through a read-only same-origin RPC. The token W price comes live from DexScreener. Nothing in the readout is modelled.
Does this measure how much money is being bridged?
No. Spanpulse measures the message rate — how many bridge transactions are landing on Solana — not the USD value moved. A busy pulse means lots of messages, which is not the same as lots of value. Treat it as a heartbeat, not a volume ledger.
Why is the flow map marked SAMPLE?
Because it is. The keyless, same-origin hosts Spanpulse is allowed to call cannot tell us which source chain each message came from. The arc animation and the Solana-side pulse scaling it are real; the per-chain weights are an illustrative concept layer, labelled wherever it appears.
Can I bridge, trade or sign anything here?
No. Spanpulse is read-only. There is no bridging, no order, no custody and nothing is minted. Connecting a wallet only reads your public balance and recent signatures — it never requests a transaction or a signature.
Do you collect anything about me?
No accounts, no tracking, no cookies. Everything runs in your browser against public, keyless endpoints and a read-only same-origin RPC proxy.
What this is, plainly
Spanpulse is a read-only concept that turns public Solana core-bridge data into a live heartbeat. The chain reads and the token price are real; the cross-chain flow map is a transparent, labelled model. Nothing here connects a wallet for signing, bridges, trades, holds funds or launches a coin. Not financial advice.