Community Event
Pulse
Observed proposal + proof timing for the latest complete Supernova finality tuple.
Transactions represented by exactly 1.000 second of accumulated observed finality across consecutive rounds; only the crossing round is prorated.
Completed transactions divided by summed observed finality time across the current rolling transaction-bearing round window.
The highest single-round fTPS observed: that round's completed transactions projected to one second at its measured finality density.
The brighter first cue marks a newly observed round.
The softer second cue follows after that round's measured finality interval.
When they nearly collapse into one sound, you’re hearing how little time separated the round from measured finality.
Recent autoPulse™️ runs
Up to the latest 100 completed autoPulse™️ runs driven by the mvxPulse operator.
Fire a Pulse
Shape a real Devnet transaction Pulse, release it against Supernova, and watch how the network responds.
| ROUND | NETWORK TX | FINALITY | fTPS |
|---|
Before your first Pulse
mvxPulse creates temporary Devnet-only transaction wallets in this browser. Sensitive wallet material is encrypted and stored locally for Pulse execution.
This notice is shown once on this browser. Accepting it does not release any transactions.
Credit your top3 Pulse?
mvxPulse now tracks the canonical observed ATH and top3 network peaks from completed Pulse diagnostics. Choose how you want credit shown if one of your Pulses qualifies.
You can change this later in Settings. Record detection continues either way; only public identity display changes.
Choose your next Pulse
Choose a tested built-in, run a local copy of the current autoPulse™, or use one of your custom profiles.
Editing: Profile
Build a Pulse. Change one variable. See what happens.
This lab uses the same runtime resolver and Pulse engine as the existing workflow. Nothing here changes Profile Workshop unless you explicitly save a profile.
Fiddle the Pulse knobs
Current profile
Profiles shape the Pulse you release
A, B and C are tested built-in Pulse shapes. AP Copy takes the current autoPulse™ settings and runs them locally as Your Pulse. Custom profiles let you change the geometry and release behavior yourself.
More wallets create more independent transaction lanes. More transactions per wallet add depth to each lane. Burst depth extends sustained pressure. Execution controls shape how tightly your browser releases that work.
Bigger numbers do not automatically mean a bigger fTPS result. Your browser shapes the release; Supernova decides how that work is absorbed across network rounds. mvxPulse enforces the limits available to your role.
Cancel preparation?
Nothing has been released. Cancelling returns directly to the original Create Pulse state.
Run a larger-than-standard Pulse?
This profile exceeds the normal 498-wallet baseline. It can materially increase preparation load, funding requirements, browser load and network impact.
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.
Reset This mvxPulse Installation?
This signs out the current X session and erases this browser’s mvxPulse installation identity, local treasury signing material, and temporary pulse wallets. The browser will restart as a new installation and require X authentication again.
Use this only to recover from a broken or stale local state. Public Devnet history and server-side records are not erased.
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.
fTPS — finality-normalized throughput
mvxPulse separates round density from ordinary wall-clock TPS so Supernova finality can be examined in its own measured time context.
One round, projected to one second
A round's completed transactions are divided by that same round's observed proposal + proof finality interval. It asks what one full second would contain if it were filled at that round's measured density. It is not an average and not a claim of sustained wall-clock TPS.
Exactly one second of accumulated finality
Consecutive rounds are accumulated until their measured finality reaches one second. The crossing round is prorated so the represented finality interval is exactly 1.000 second.
Advanced: calculation boundaries
round transactions ÷ (round proposal + proof finality in seconds)
full transactions from consecutive rounds + prorated crossing-round transactions, normalized to exactly 1.000 s of accumulated finality
Only rounds with trustworthy positive finality timing participate. mvxPulse does not substitute the nominal round duration for missing finality evidence.
These metrics describe observed finality density. They should not be presented as sustained network TPS across ordinary wall-clock time.
Make Supernova tangible.
mvxPulse turns live public MultiversX Devnet telemetry into something you can see, hear, explore — and participate in.
The grid is live network data. When you fire a Pulse, your browser adds real Devnet transactions to what you are watching.
Bring your handle.
X sign-in gives mvxPulse a lightweight participant identity and helps keep Pulse access tied to real people rather than anonymous automated traffic.
Your Pulses can also qualify for the mvxPulse Observed ATH and top3 records. You choose whether those records show your full handle, a masked handle, or remain anonymous.
No MultiversX wallet required.
When you prepare a Pulse, mvxPulse creates and manages Devnet-only wallets locally inside this browser.
It checks their state, supplies test xEGLD when needed, signs the transactions locally, and prepares them for the target network round.
You do not need to provide EGLD, import a wallet, or manually manage transactions.
Pick a profile. Fire. Watch.
- 1Tap FIRE A PULSE.
- 2Choose a profile — the built-ins are a good place to start — and let mvxPulse prepare the Pulse.
- 3When preparation finishes, use the on-screen ARM control for your own timing, or join crowdPulse™ when a public Pulse is available.
mvxPulse handles the round timing and releases the prepared transactions against Supernova. Keep the page open while a Pulse is preparing or active.
Now watch what happened.
The grid shows how transactions were absorbed across the observed network rounds. Look for Peak Network Round · Largest TX Round · Finality · Completion · Observed ATH.
Sound makes the timing easier to feel: the first tone marks the observed round; the softer second tone follows after its measured finality interval.
Every Pulse also leaves a diagnostic record you can inspect and share.
Supernova, alive.
This sphere is an interpretive view driven by live MultiversX telemetry. Its geometry is illustrative; the rounds, activity and timing are real when the feed is live. Drag to rotate · scroll or pinch to zoom.
This browser installation
Identity, Pulse behavior, records, local data and browser-local Devnet resources for this installation.
- BROWSER
- —
- INSTALLATION
- —
- BALANCE
- —
- ADDRESS
—
ADVANCED ADMIN · CROWD DIAGNOSTICS
TECHNICAL / EXPORT
JSON export is available for analysis, support, or archival use.- APP
- —
- NETWORK
- MultiversX Devnet
- BROWSER
- —
- INSTALLATION
- —
- WALLET POOL
—
Your recent Pulses
Your recent Pulses, crowdPulse™ participation and public autoPulse™ results — with the network evidence saved for each run.
Pulse Detail
Complete record for this Pulse.
My Pulses
Pulses saved on this device. Open any result to review it or create a share graphic.
TECHNICAL / EXPORT
Pulse Record
Why I built mvxPulse™️
I wanted a way to make Supernova’s speed feel tangible, not just describe it with numbers. I also wanted to give the community a way to come together and make some noise, similar to what I did with Guardian and EGLDHeist.
mvxPulse 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.
The grid is live data. There is no pretence, no augmentation, nothing faked here. And the engineer’s version will even let the core team play.
This is an independent experiment built to help people explore, understand, and share what Supernova is doing as it develops.
Make no mistake: Supernova changes blockchain. Blockchain just doesn’t know it yet.
But it will.
Thanks to everyone who supports me, my compadres, and MultiversX.
What you’re actually seeing
Live network data: rounds, shard activity, block data, validator/telemetry state and timing come from public MultiversX Devnet sources when those sources are reachable.
Interpretive presentation: the sphere, arcs, spacing and visual choreography are not a geographic map. They are a visual language for showing Supernova activity and parallelism.
Why several areas move at once: MultiversX shards and the metachain operate in parallel. mvxPulse reflects that rather than pretending the network is one sequential stream.
Finality + sound: when sound is enabled, the first cue marks a newly observed round. The softer second cue follows after that round’s measured finality interval.
Truth matters here: if mvxPulse says a feed is live, the underlying telemetry is real. When live observation is unavailable, the interface should say so rather than inventing activity. Visual choreography remains interpretive where a dedicated observer feed is not available.
View controls: use the shard buttons to isolate a region. Your choice is saved locally and restored after refresh.