What is a hash? (No maths) A wax seal that breaks if you change one letter
A hash is a short fingerprint of any piece of data. The same data always gives the same fingerprint, and changing even one letter gives a completely different one. Blockchains use hashes as seals that show at once if anything was altered.
Ben owes Anna ten coins. It's written in the notebook in his own hand: "Ben owes Anna 10". One evening, he borrows the notebook and carefully scratches out the zero. Now it says "Ben owes Anna 1". Nobody will notice a missing zero.
Except that at the bottom of the page there's a wax seal. It was pressed from the page itself, and every house has a drawing of it. Ben's page now makes a completely different seal. Not slightly different. Different from top to bottom, like a seal from another village.
That's a hash: a seal, or a fingerprint, of a piece of data. You can't see the page in it. But you can see at once whether the page is the one that made it.
What it is
A hash is a short code that a fixed recipe, called a hash function, makes from any data: a sentence, a file, a whole block. Think of it as the data's fingerprint. A person has one fingerprint; a fingerprint doesn't tell you their name, but it tells you whether it's the same person.
Bitcoin uses a recipe called SHA-256, published by the US standards agency NIST. Its standard says what hashes are for: "The digests are used to detect whether messages have been changed since the digests were generated" (NIST FIPS 180-4). "Digest" is the standard's word for the hash.
How it works: three seals, three properties
You don't need to understand the recipe to see what it does. Here are real SHA-256 hashes, which you can check yourself (see the end of the article). Each one is 64 characters long; here are the first 16.
- "Ben owes Anna 10" gives 0cf204b5605c824f...
- "Ben owes Anna 1" gives 9251c83b36c9d7a2...
- "ben owes Anna 10", with a small b, gives d3036d304dd78712...
Three properties fall out of this.
- Same page, same seal. Hash "Ben owes Anna 10" today, tomorrow or on another computer, and you get 0cf204b5 every time. That's why thousands of nodes can compare seals without comparing whole pages.
- Tiny change, totally different seal. One missing zero, or one small letter, and nothing in the seal resembles the old one. NIST's standard puts it soberly: "any change to the message will, with a very high probability, result in a different message digest" (NIST FIPS 180-4).
- No going backwards, no forging. From a seal you can't rebuild the page, and you can't design a second page with the same seal. The standard calls both "computationally infeasible": to find a message for a given digest, or "two different messages that produce the same message digest" (NIST FIPS 180-4).
One more: the size never changes. "The final result of SHA-256 is a 256-bit message digest", which is written as 64 characters (NIST FIPS 180-4). Ben's five-word sentence and a whole block of payments get seals of the same size.
Where the seals sit in a blockchain
Bitcoin uses seals everywhere. Every transaction is known by its hash. Every block is too: the header of block 900,000, added on 6 June 2025, hashes to a seal that starts 000000000000000000010538edbf (mempool.space). Bitcoin runs SHA-256 twice on each header, which the developer reference writes as SHA256(SHA256()) (Bitcoin developer reference).
And every block carries the seal of the block before. The white paper describes it: each timestamp "includes the previous timestamp in its hash, forming a chain" (Nakamoto, 2008). Change one old page and its seal changes, so the next page's copy of that seal no longer matches. That's the next article.
Why it matters
- Checking is cheap. Comparing two 64-character seals takes a moment. Comparing two full copies of the Bitcoin notebook line by line doesn't.
- Tampering is loud. A forger can't make a small change look small. One digit, and the seal shouts.
- It's the same recipe in many places. SHA-256 is a public standard. The same idea is used to check software downloads and documents, far beyond crypto.
Where people get it wrong
- "A hash is encryption." Encryption can be undone with a key. A hash can't be undone at all. It's a seal, not a lock.
- "A hash hides the data." Not for short, guessable data. Anyone can hash "Ben owes Anna 1", "Ben owes Anna 2" and so on until one matches. The seal protects against changes, not against guessing.
- "Similar data gives a similar hash." The opposite. That's the whole point.
- "Hashes look random, so they mean nothing." They look random, but they're fixed. The same input gives the same hash for everyone, everywhere.
The sting: press the seal yourself
Search the web for "SHA-256 online" and type "Ben owes Anna 10". If you have Python, this one line does the same: python3 -c "import hashlib; print(hashlib.sha256(b'Ben owes Anna 10').hexdigest())". You should see 0cf204b5 at the start. Now remove the zero.
That's the whole trick, and it costs nothing. When the stranger at the gate says his records are "secured by advanced cryptography", ask him which hash, and what it's a hash of. Hashing is free. So, it turns out, is the phrase "advanced cryptography".
Frequently asked questions
What is a hash in simple terms?
A hash is a short fingerprint of a piece of data, made by a fixed recipe called a hash function. The same data always gives the same hash, and any change to the data gives a completely different one.
What is SHA-256?
SHA-256 is a hash function published by the US National Institute of Standards and Technology in its Secure Hash Standard, FIPS 180-4. It turns any input into a 256-bit result, usually written as 64 characters. Bitcoin uses it for transaction and block hashes.
Can you reverse a hash?
No. NIST's standard says it is computationally infeasible to find a message that matches a given SHA-256 hash. Short, predictable inputs can still be guessed by trying candidates, so a hash isn't a way to hide secrets.
Why do blockchains use hashes?
Hashes let every node check quickly whether data has changed. Each block includes the hash of the previous block, so changing an old block breaks the link to every block after it.
Is a hash the same as encryption?
No. Encrypted data can be turned back into the original with the right key. A hash can't be turned back into anything. It only proves whether data matches the original.

