<p>If you are solo mining, hashes mean nothing. Whether you have a 19t/h rig or a 1m/h rig, both have the same chance of finding the correct hash to solve a block. Pool mining, true, the higher your hash rate, the better.  Solo mining, hash rate is not relevant.</p>

CC BY-SA 4.0
2022-04-03T23:00:24.897Z
This is completely false. The higher your hashrate is, the higher the probability of finding a winning block per unit of time.
Pieter Wuille
CC BY-SA 4.0
2022-04-03T20:39:25.083Z
2022-04-03T20:39:25.083Z
Fred Flintstone
<p>Well, currently the difficulty is 2,440,643.  There will be (difficulty * 2^32) (roughly) hashes per block.  </p>

<p>So that means there are (2,440,643 * 2^32) hashes that must occur before one block is solved.  That's is across the entire network.</p>

<p>A block is solved in ten minutes (on average) or 600 seconds.<br>
So the network is hashing (2,440,643 * 2^32) / 600  ~= 17 Thash/s.  (This calculation is performed and the result is displayed on BitcoinWatch.com)</p>

<p>Let's say your dual 5970 rig gets 1.4 Ghash/s.  That is 17,770 Ghash/s / 1.4 Ghash/s = 12,693.  That is the number of rigs, if all were exactly like yours, operating today.  </p>

<p>So if 12,693 rigs can do the work in 10 minutes, one solo rig will tka 12,693 * 10 minutes, or 126,930 minutes.    With 1,440 minutes in a day, that means it will be about 88 days before you will have a 50% chance of solving a block operating solo.</p>

<p>Now that was the long way.</p>

<p>The short way:</p>

<ul>
<li><a href="http://tpbitcalc.appspot.com/" rel="noreferrer">http://tpbitcalc.appspot.com/</a></li>
</ul>

<p>For Hash Rate, plunk in 1400 (1.4 Ghash/s) and click Calculate.</p>

<p>So then, how many hashes is that?  There are 86,400 seconds in a day and you have to has for 88 days.  86,400 * 88 = 7,603,200 seconds.  At 1.4 Ghash/s X 7,603,200 seconds means you hashed 10,644 Thashes. </p>

<p>That is: 10,644,000,000,000,000 hashes.</p>

CC BY-SA 3.0
2012-08-27T10:24:31.213Z
Since it takes the network `2^32 * difficulty` hashes to find a block on average, it will also take you `2^32 * difficulty` hashes to find a block on average, roughly. So you can take the current difficulty, multiply by about 4.3 billion, and that's how many hashes you will need, on average, to find one block. (Assuming the difficulty doesn't change on you.)
David Schwartz
CC BY-SA 3.0
2012-08-27T09:14:09.563Z
2012-08-27T10:23:01.107Z
2012-08-27T10:23:01.107Z
Stephen Gornick
<p>I'm toying with the idea of starting to mine, and was wondering how to calculate how many hashes on average must be tried before one will "hit" a valid block?  I'm talking about a single user (not a pool) using one rig.</p>

CC BY-SA 3.0
2012-08-27T18:43:37.840Z
I rephrased the question to make it general instead of specific to the current point in time, to make it more useful for future visitors.
D.H.
<difficulty><mining-profitability><hashpower>
Calculating average number of hashes tried before hitting a valid block
Baard Kopperud
# Calculating average number of hashes tried before hitting a valid block

(Asked by: username_0 on 2012-08-27)

I'm toying with the idea of starting to mine, and was wondering how to calculate how many hashes on average must be tried before one will "hit" a valid block? I'm talking about a single user (not a pool) using one rig.

**Tags:** difficulty, mining-profitability, hashpower

> **Comments:**
> **username_1**: I rephrased the question to make it general instead of specific to the current point in time, to make it more useful for future visitors.  

---

## 2 answers

### Answer by username_4 on 2012-08-27. Score: 10 | Accepted answer

Well, currently the difficulty is 2,440,643. There will be (difficulty \* 2^32) (roughly) hashes per block.

So that means there are (2,440,643 \* 2^32) hashes that must occur before one block is solved. That's is across the entire network.

A block is solved in ten minutes (on average) or 600 seconds.  
So the network is hashing (2,440,643 \* 2^32) / 600 ~= 17 Thash/s. (This calculation is performed and the result is displayed on BitcoinWatch.com)

Let's say your dual 5970 rig gets 1.4 Ghash/s. That is 17,770 Ghash/s / 1.4 Ghash/s = 12,693. That is the number of rigs, if all were exactly like yours, operating today.

So if 12,693 rigs can do the work in 10 minutes, one solo rig will tka 12,693 \* 10 minutes, or 126,930 minutes. With 1,440 minutes in a day, that means it will be about 88 days before you will have a 50% chance of solving a block operating solo.

Now that was the long way.

The short way:

* <http://tpbitcalc.appspot.com/>

For Hash Rate, plunk in 1400 (1.4 Ghash/s) and click Calculate.

So then, how many hashes is that? There are 86,400 seconds in a day and you have to has for 88 days. 86,400 \* 88 = 7,603,200 seconds. At 1.4 Ghash/s X 7,603,200 seconds means you hashed 10,644 Thashes.

That is: 10,644,000,000,000,000 hashes.

> **Comments:**
> **username_5**: Since it takes the network `2^32 * difficulty` hashes to find a block on average, it will also take you `2^32 * difficulty` hashes to find a block on average, roughly. So you can take the current difficulty, multiply by about 4.3 billion, and that's how many hashes you will need, on average, to find one block. (Assuming the difficulty doesn't change on you.)  

---

### Answer by username_2 on 2022-04-03. Score: -3

If you are solo mining, hashes mean nothing. Whether you have a 19t/h rig or a 1m/h rig, both have the same chance of finding the correct hash to solve a block. Pool mining, true, the higher your hash rate, the better. Solo mining, hash rate is not relevant.

> **Comments:**
> **username_3**: This is completely false. The higher your hashrate is, the higher the probability of finding a winning block per unit of time.  

---

