Session setup
Ready to simulate proof of work without mining a real cryptocurrency.
Educational component
Interactive proof-of-work simulator
This page only simulates local hash search inside the browser tab. It does not connect to a blockchain, a pool or a real wallet.
Important: the wallet field is just a label to personalize the session summary. No coins are mined, sent or received.
Live metrics
Tried hashes0
Current nonce0
Approx. hash rate0 h/s
Elapsed time0.00 s
Best score: 0 / 4
Best hash:...
Recent attempts
Start the simulation to see hash attempts appear here.
What this demonstrates
- Each nonce changes the input string and therefore the resulting SHA-256 hash.
- Difficulty is modeled as the number of leading zeroes required at the start of the hash.
- The work happens locally in your tab and stops as soon as a valid demo hash is found.
- It is a teaching aid to understand proof of work, not a real mining client.
Why a simulator is better than real browser mining
Real browser mining transfers an economic cost to the visitor: CPU cycles, battery, heat and lower performance. A simulator keeps the useful learning goal without connecting to a pool or creating a hidden monetization mechanism.
This distinction matters for security and SEO. A page that clearly explains what it does, why it does it and how to stop it is much easier to trust than a page that silently runs expensive JavaScript.
How to read the metrics
- Tried hashes show the amount of candidate nonces tested in this browser tab.
- Difficulty is intentionally small so the demo finishes quickly and does not punish the device.
- Approximate hash rate depends on the browser, device, battery mode and other open tabs.
- A solved nonce is only valid for the local demo message, not for a real blockchain.
Classroom use and ethical limits
This simulator is useful when the goal is to explain hashes, nonces and difficulty without asking students or visitors to run a real monetization script. It can be used as a short classroom exercise: change the message, increase the difficulty one step at a time and compare how the number of attempts grows.
The ethical boundary is simple: a website should never consume meaningful CPU in the background without clear consent, visible controls and a legitimate purpose. For that reason this page keeps the work local, limited and explicit.