<p><a href="https://bitcoin.stackexchange.com/questions/35699/what-is-a-block/35700#35700">StephenM wrote a good answer to that:</a></p>

<blockquote>
  <ol start="5">
  <li>The difficulty (or nBits as it is called in the code) is shorthand for how difficult it is to solve the block. Essentially, it encodes a target value, and the hash of the block (when treated as a 256 bit integer) must be below that target value to be considered solved.</li>
  </ol>
</blockquote>

CC BY-SA 3.0
2015-12-18T01:32:36.597Z
2015-12-18T01:32:36.597Z
2017-04-13T12:47:36.707Z
Nick ODell
<p>The other nodes can verify it by hashing the block using the supposed solution nonce, and if it returns the same hash as the solution, and it meets the difficulty restrictions (correct number of zeroes at the beginning), the that block is confirmed as solved.</p>

CC BY-SA 4.0
2016-02-04T20:01:15.660Z
2019-07-10T18:27:20.690Z
2019-07-10T18:27:20.690Z
redOctober13
<p>Let's say block #396716 has been just mined. The participants verify:</p>

<ol>
<li><p>Is the block really next? Simply look if the previous block is already accepted. Each block contains the ID of previous block.</p></li>
<li><p>Has miner performed enough work? Because difficulty is now 120 this means there should be 120÷8 = 15 zeroes in the block ID.</p></li>
</ol>

<p>00000000000000000277e25b11ccc9dc44a8563de315c454507522dae5a0d204</p>

<p>000000000000000 &lt;- 15 zeroes. Therefore miner spent enough work.</p>

<ol start="3">
<li>Is the timestamp correct? Just test if it's near current time.</li>
<li>Verify all transactions inside the block. This includes checking if miner sent himself the correct reward (currently 25 BTC). Next, all transactions are checked, if amounts match, signatures correct, etc..</li>
</ol>

CC BY-SA 3.0
2016-02-08T12:46:39.780Z
That's not how difficulty works. It's not expressed as a number of zeroes at the start, but as a ratio between the maximum block hash and the actually required one.
Pieter Wuille
CC BY-SA 3.0
2016-02-04T20:38:13.390Z
2016-02-04T20:38:13.390Z
Anlhord Smithson
<p>when a miner solves a block it gets sent out to the network, when other nodes receive it, how do they verify that the block received was indeed solved and can be added to the blockchain.</p>

<p>So you don't know what the answer is but if you got the answer you know what the question was.</p>

<blockchain><block><verification><consensus>
how do nodes verify that a block has been solved and can be added to the blockchain
hash tables
# how do nodes verify that a block has been solved and can be added to the blockchain

(Asked by: username_0 on 2015-12-17)

when a miner solves a block it gets sent out to the network, when other nodes receive it, how do they verify that the block received was indeed solved and can be added to the blockchain.

So you don't know what the answer is but if you got the answer you know what the question was.

**Tags:** blockchain, block, verification, consensus


---

## 3 answers

### Answer by username_1 on 2015-12-18. Score: 2

[StephenM wrote a good answer to that:](https://bitcoin.stackexchange.com/questions/35699/what-is-a-block/35700#35700)

> 5. The difficulty (or nBits as it is called in the code) is shorthand for how difficult it is to solve the block. Essentially, it encodes a target value, and the username_0 of the block (when treated as a 256 bit integer) must be below that target value to be considered solved.


---

### Answer by username_2 on 2016-02-04. Score: 1

The other nodes can verify it by hashing the block using the supposed solution nonce, and if it returns the same username_0 as the solution, and it meets the difficulty restrictions (correct number of zeroes at the beginning), the that block is confirmed as solved.


---

### Answer by username_3 on 2016-02-04. Score: -1

Let's say block #396716 has been just mined. The participants verify:

1. Is the block really next? Simply look if the previous block is already accepted. Each block contains the ID of previous block.
2. Has miner performed enough work? Because difficulty is now 120 this means there should be 120÷8 = 15 zeroes in the block ID.

00000000000000000277e25b11ccc9dc44a8563de315c454507522dae5a0d204

000000000000000 <- 15 zeroes. Therefore miner spent enough work.

3. Is the timestamp correct? Just test if it's near current time.
4. Verify all transactions inside the block. This includes checking if miner sent himself the correct reward (currently 25 BTC). Next, all transactions are checked, if amounts match, signatures correct, etc..

> **Comments:**
> **username_4**: That's not how difficulty works. It's not expressed as a number of zeroes at the start, but as a ratio between the maximum block username_0 and the actually required one.  

---

