Bitcoin Forum
December 05, 2016, 12:37:55 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: 17 blocks in the last hour?  (Read 2897 times)
Raulo
Full Member
***
Offline Offline

Activity: 238


View Profile
February 24, 2011, 09:52:41 PM
 #21

The largest time with no blocks in the recent history (not counting difficulty = 1 prehistory) was slightly above 2 hours:
http://blockexplorer.com/b/105909

The probability of such long time without blocks is 1:160000 assuming 6 blocks/hour hashspeed.

There was a 7h time between blocks at
http://blockexplorer.com/b/74638

but I guess this was due to the infamous bug in pre-0.3.9 bitcoin.

1HAoJag4C3XtAmQJAhE9FTAAJWFcrvpdLM
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480898275
Hero Member
*
Offline Offline

Posts: 1480898275

View Profile Personal Message (Offline)

Ignore
1480898275
Reply with quote  #2

1480898275
Report to moderator
1480898275
Hero Member
*
Offline Offline

Posts: 1480898275

View Profile Personal Message (Offline)

Ignore
1480898275
Reply with quote  #2

1480898275
Report to moderator
1480898275
Hero Member
*
Offline Offline

Posts: 1480898275

View Profile Personal Message (Offline)

Ignore
1480898275
Reply with quote  #2

1480898275
Report to moderator
theGECK
Sr. Member
****
Offline Offline

Activity: 410



View Profile
February 24, 2011, 09:54:03 PM
 #22

So, when slush's pool was working for 10 hours, it just meant that they hadn't found the answer to a block in that amount of time. The entire time, blocks were being discovered, and that information was being updated into the pool so they could try to find the next one. Correct?

Use my referral codes for Bitcoin faucets and I'll send you 25% of my referral bonus - Win/Win! PM for details on all sites available or use one of the links here.

FreeBitco.in | FreeDoge.co.in
eMansipater
Sr. Member
****
Offline Offline

Activity: 294



View Profile WWW
February 24, 2011, 10:35:44 PM
 #23

So, when slush's pool was working for 10 hours, it just meant that they hadn't found the answer to a block in that amount of time. The entire time, blocks were being discovered, and that information was being updated into the pool so they could try to find the next one. Correct?
Precisely.

If you found my post helpful, feel free to send a small tip to 1QGukeKbBQbXHtV6LgkQa977LJ3YHXXW8B
Visit the BitCoin Q&A Site to ask questions or share knowledge.
0.009 BTC too confusing?  Use mBTC instead!  Details at www.em-bit.org or visit the project thread to help make Bitcoin prices more human-friendly.
bitjet
Hero Member
*****
Offline Offline

Activity: 556


View Profile
February 25, 2011, 05:23:09 AM
 #24

I've been lucky today. Just started my first ever solo mining attempt today. Hit my first block in the first 12 hours. 8 hours later I shut down the miners to do somthing, when I finally got them going a few minutes ago and literally a minute into it I hit another block... Shit I just looked at the screen THREE MORE BLOCKS WTF?


... ok that last sentence was complete bs, but I feel like I nailed a solo block now I should jsut jump back in the pool for 24 hours, then hit the solo miners again for 24 hours. Alternation maybe my luck?

What block is next diff?
FreeMoney
Legendary
*
Offline Offline

Activity: 1246


Strength in numbers


View Profile WWW
February 25, 2011, 07:41:52 AM
 #25



What block is next diff?


Take current number of blocks and divide by 2016. The decimal part tells you the % of the way to the next diff update. Subtract it from 1 and multiply that decimal by 2016 to get blocks to next diff update.

Play Bitcoin Poker at sealswithclubs.eu. We're active and open to everyone.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!