The brighter first cue marks a newly observed round.
The softer second cue follows after that round's measured finality interval.
When the two sounds nearly collapse into one, your ear is hearing just how small the finality delay is.
Share this moment
Frozen exactly when you tapped Share.
Fire a Pulse
Send a coordinated burst of test transactions and watch MultiversX Supernova answer live.
| ROUND | NETWORK TX | FINALITY | FTPS |
|---|
My Pulse Wallets
Loading the encrypted local wallet inventory…
Delete Local Wallets?
This permanently removes the signing material for the temporary Devnet wallets stored in this browser. Their addresses and public blockchain history will continue to exist on MultiversX.
This cannot be undone.
Pulse Lab
Balanced disposable wallets across S0, S1 and S2. Private keys stay in local external state.
npm run pulse:lab
Or next time start both mvxPulse + Pulse Lab with:
npm run dev:lab
Generates addresses until each execution shard has the requested wallet count. Creation does not move treasury funds; the pulse protocol funds only the selected cohort when needed.
PULSE performs reserve → preflight → fund deficits → verify → send → release automatically.
CTPS & FTPS
Two ways to describe what the network actually did — without relying on headline theoretical TPS claims.
Completed Transactions Per Second
CTPS measures how quickly transactions were actually completed during transaction-bearing rounds. Empty rounds are ignored because no transactions were completed in them.
Finality Transactions Per Second
FTPS measures those completed transactions against the actual finality time recorded for the same rounds. It shows completed transaction activity per second of measured finality.
Advanced: how mvxPulse calculates them
{ round, txCompleted, finalityMs, roundTimestampMs, observedAt }
completed tx in active rounds ÷ actual elapsed block/round time for those active rounds
completed tx in active matched rounds ÷ summed finality time for those exact rounds
A round must contain at least one completed transaction to participate in either rate. FTPS additionally requires matching finality data for that exact round. Empty rounds remain visible in the matrix and history, but never dilute CTPS or FTPS.
FTPS is not MultiversX's advertised theoretical TPS. It is calculated from live, observed completion and finality data collected by mvxPulse.
See — and hear — Supernova finality.
mvxPulse turns live MultiversX Supernova telemetry into a visual and audible network pulse.
The sound is part of the experience: a brighter first tone marks a newly observed round. A softer second tone follows after that round's measured finality interval.
When Supernova is finalizing in roughly 80–100 ms, those two sounds nearly collapse into one. Your ear is hearing how little time separates the events.
Supernova, alive.
This sphere is an interpretive view driven by live MultiversX telemetry. Its geometry is illustrative; the observed rounds, activity, proposer events, and timing come from the network. Drag to rotate · scroll or pinch to zoom.
Your observation window
The headline AVG and rolling statistics are calculated from the finality rounds you observe in mvxPulse.
Stored observations never leave this browser. They are not an authoritative historical network dataset.
Why I built this
I wanted a way to make Supernova's speed feel tangible, not just describe it with numbers.
This visualization takes live public MultiversX Devnet telemetry and turns it into something you can watch — and, with sound enabled, something you can almost physically sense. The first tone marks the round; the softer second tone arrives after the measured finality interval.
The sphere itself is interpretive rather than geographic, but the telemetry underneath it is real wherever the interface says it is live.
This is an independent experiment made to help people explore, understand and share what Supernova is doing as it develops.
About this visualization
What is real: live MultiversX Devnet node inventory when reachable, shard membership, round / epoch context, the public heartbeat-derived layer of eligible validators, and the block viewport fed from public shard-block queries when available.
What is interpretive: the sphere layout, spacing, arcs, and pulse choreography. This is a protocol visualization, not a physical map of where machines live on Earth.
Why multiple regions pulse: MultiversX execution shards and the metachain all operate in parallel. This visualization shows that parallelism continuously instead of implying that only one shard is alive.
What is still approximate: without running one observer per shard, the per-shard pulse choreography outside the directly queried telemetry shard is an architecture-grounded representation rather than a direct stream from four separate observer feeds.
Hear the speed: when sound is enabled, the first cue marks a newly observed round. A softer second cue is delayed by that round's measured finality interval. The audible spacing is derived from live telemetry; playback begins when the browser receives the sample, so it is a sonification of measured latency rather than a literal replay of the original network timestamps.
View controls: use the shard buttons to isolate a region. Your choice is saved locally and restored after refresh.