why is there one hour gap between blocks that are mined?

pooya87

legendary

Activity: 3472

Merit: 10611

ok let me explain to you all what rank means on a forum:
it doesn't mean i am a bitcoin developer now, or have a complete knowledge or understanding of bitcoin and how it works,... and never claimed it either!
it only means that i have been Using bitcoin and bitcointalk for a long time.

and although i am interested in learning about the technical stuff about bitcoin and have also gathered some knowledge over the years i still don't know everything about bitcoin and there are still lots of things i don't know or misunderstood after i read things. which might sound to you as "basic"

and in the end i am mostly interested in using bitcoin not learning every single detail about it, i only know and am interested to know what seems important or interesting to know Cheesy

and just FYI, i own this account from 2014-9

BurtW

legendary

Activity: 2646

Merit: 1137

All paid signature campaigns should be banned.

Quote from: Jet Cash on May 26, 2016, 09:08:39 AM

Yet another reason to increase the average block generation frequency.

No, it is not a reason to do anything. It is a question about how Bitcoin works.

Answer: just fine, as designed, as expected, nothing new, long blocks happen at the expected frequency, nothing needs to be "fixed", Bitcoin has worked like this for years and will continue to work just fine, as is, for many more years.

If you want an increased block frequency use another coin. There are plenty of them with a faster block time.

Jet Cash

legendary

Activity: 2814

Merit: 2472

https://JetCash.com

Yet another reason to increase the average block generation frequency.

tobacco123

sr. member

Activity: 552

Merit: 250

Quote from: Lauda on May 26, 2016, 08:00:08 AM

Here you can find some useful function regarding exponential distribution. I've posted these images recently in another thread:

Read[1]:

Quote

There are lots of block intervals with a time less than 10 minutes but then a few block intervals much longer which bump up the average to 10 minutes. So the bitcoin network can get unlucky and a block won't be found for a whole hour.

[1] - https://en.bitcoin.it/wiki/Confirmation#Confirmation_Times

These are extremely useful graphs to demonstrate that the AVERAGE block time is 10 minutes. By chance can take as long as it wants- 1 hour for 1 block is rare but it happens now and then by chance.

Lauda

legendary

Activity: 2674

Merit: 2965

Terminated.

Here you can find some useful function regarding exponential distribution. I've posted these images recently in another thread:

Read[1]:

Quote

There are lots of block intervals with a time less than 10 minutes but then a few block intervals much longer which bump up the average to 10 minutes. So the bitcoin network can get unlucky and a block won't be found for a whole hour.

[1] - https://en.bitcoin.it/wiki/Confirmation#Confirmation_Times

BurtW

legendary

Activity: 2646

Merit: 1137

All paid signature campaigns should be banned.

1. The ability to buy Hero an even Legendary accounts + signature campaigns for Hero and Legendary accounts = market for accounts + signature spam + noobs owning Hero accounts

2. Hero accounts should be answering basic questions like this not asking them

3. You are a noob that bought a Hero account just to spam your signature to make a profit

Have you made a profit on your purchased account yet?

rizzlarolla

hero member

Activity: 812

Merit: 1001

Quote from: pooya87 on May 26, 2016, 04:49:21 AM

thanks you franky1 for the explanation.

Quote from: rizzlarolla on May 26, 2016, 03:26:41 AM

"Hero member", sig campaign, nearly 3000 posts... yet not a clue of Bitcoin basics.
This is disgraceful.
This "1 hour" block prop, or "1 miniute" block prop has always been, and will always be.
Now you noticed?
Clueless sig campaign hero BCT members, helping to destroy BCT credibility.
PLEASE REVOKE THIS USERS "HERO MEMBERSHIP" Huh

seriously.

if you think asking about a simple thing that i have never noticed before in the past two years in bitcoin destroys BCT credibility then you are clueless.

If it took you 2 years and 3000 posts to notice this most simple basic thing is happening and not understand why,
I think we can see who is clueless here.

pooya87

legendary

Activity: 3472

Merit: 10611

thanks you franky1 for the explanation.

Quote from: rizzlarolla on May 26, 2016, 03:26:41 AM

"Hero member", sig campaign, nearly 3000 posts... yet not a clue of Bitcoin basics.
This is disgraceful.
This "1 hour" block prop, or "1 miniute" block prop has always been, and will always be.
Now you noticed?
Clueless sig campaign hero BCT members, helping to destroy BCT credibility.
PLEASE REVOKE THIS USERS "HERO MEMBERSHIP" Huh

seriously.

if you think asking about a simple thing that i have never noticed before in the past two years in bitcoin destroys BCT credibility then you are clueless.

rizzlarolla

hero member

Activity: 812

Merit: 1001

"Hero member", sig campaign, nearly 3000 posts... yet not a clue of Bitcoin basics.
This is disgraceful.

This "1 hour" block prop, or "1 miniute" block prop has always been, and will always be.
Now you noticed?

Clueless sig campaign hero BCT members, helping to destroy BCT credibility.

PLEASE REVOKE THIS USERS "HERO MEMBERSHIP" Huh

seriously.

franky1

legendary

Activity: 4410

Merit: 4766

the time is semi-random but based on the maths that the probability of 2016 blocks will be found over a two week period. and an adjustment of the difficulty to make it easier to make 2016 blocks over 2 weeks or harder to make 2016 blocks over 2 weeks.

no where in the code does it state 10 minutes.(that is just a human calculation away from the code)

however the probability of 2016 blocks over 2weeks (statistically, human calculated but not in code) works out as 1 block per 10 minutes.
but when it comes to the code and the rules of mining.. the blocks can be made in a couple minutes or couple hours. but has a bit of difficulty tha doesnt make it totally random

its this difficulty variable that is adjusted to make it harder if more then 2016 blocks are made over 2 weeks. or adjusted to make it easier if less then 2016 blocks are made over 2 weeks

again no where in the code does it state a block is made in 10 minutes.. instead its 2016 blocks over a 2 week period

odolvlobo

legendary

Activity: 4466

Merit: 3391

Quote from: ?? on ??

Sometimes too many fake transactions in network or too many ddos attempts, that's why it might take longer for a block to be found.

No that is not why at all. The time is random, but the average is about 10 minutes, Sometimes it takes 30 seconds. Sometimes it takes an hour.

pooya87

legendary

Activity: 3472

Merit: 10611

Quote from: Digital_Lord on May 26, 2016, 02:15:23 AM

A New block just mined 2 minutes before. and previous block was mined 5 minutes before. only 3 minutes deference between them, seems now everything is working fine...
I am also wondering what happened with mining pools. why it stopped for almost one hour. why blocks are stopped for one hour.. Huh

yeah i edited my post to change the title so that it matches the current situation.

i don't know if this has happened before or not but i have never seen more than 20 min gap between blocks.

Digital_Lord

hero member

Activity: 1498

Merit: 502

👉bit.ly/3QXp3oh | 🔥 Ultimate Launc

A New block just mined 2 minutes before. and previous block was mined 5 minutes before. only 3 minutes deference between them, seems now everything is working fine...
I am also wondering what happened with mining pools. why it stopped for almost one hour. why blocks are stopped for one hour.. Huh

korila

member

Activity: 107

Merit: 10

after an hour now it has just mined 1 block . omfg

pooya87

legendary

Activity: 3472

Merit: 10611

the new blocks are supposed to be mined every 10 minutes but sometimes i see shorter or longer time between blocks but right now the last block was mined about an hour ago?

what is up?

EDIT:

can anyone explain why this happened?

Topic: why is there one hour gap between blocks that are mined? (Read 779 times)