No blocks since in the last hour | Bitcointalksearch.org

odolvlobo

legendary

Activity: 4466

Merit: 3391

Quote from: OmegaStarScream on November 19, 2016, 07:45:39 AM

How come no blocks were found in the last 55 minutes (to be accurate) while the average should be 10 minutes
....

Somebody doesn't understand the word "average".

Quote from: OmegaStarScream on November 19, 2016, 07:45:39 AM

....
EDIT : Two blocks was found (2 minutes between them) , not sure what's going on here.

For someone with so many posts, I'm surprised that you have no idea how Bitcoin works.

CoinCidental

legendary

Activity: 1316

Merit: 1000

Si vis pacem, para bellum

Quote from: rapazev on November 19, 2016, 03:42:25 PM

i'm not an expert, but when the nodes are updating they cant confirm transactions, can they?

A node can update its client in couple of minutes, they can use their existing blockchain and update the client so it shouldn't affect confirmation times..... Also all ~5500 nodes will not choose to update at the exact same time

While we are on the subject more new people should run a full node to help strengthen the network, just open port 8333 on the router and you will be doing your bit to help btc stay secure and fast, if anyone needs help just mention it here, I or someone else will be happy to help

TastyChillySauce00

legendary

Activity: 3010

Merit: 1028

Leading Crypto Sports Betting & Casino Platform

Quote from: Cashew on November 19, 2016, 05:56:57 PM

At least I learnt something today. I thought that there was exactly 10 minutes between each block but it seems it isn't the case.

well the block is not exactly coming every 10 minutes but 10 minutes is just an average when the block will be coming and ready to be solved by the miners,it may either more or less
as Yuuto stated above,it's like a luck game

Yuuto

hero member

Activity: 644

Merit: 501

Quote from: OmegaStarScream on November 19, 2016, 07:45:39 AM

How come no blocks were found in the last 55 minutes (to be accurate) while the average should be 10 minutes . In the meantime , number of unconfirmed transaction is 11,000 and increasing... https://blockchain.info/unconfirmed-transactions I will assume It has nothing to do with SegWit and wait for a logical explanation .

EDIT : Two blocks was found (2 minutes between them) , not sure what's going on here.

https://blockchain.info/block/000000000000000001ed495dc3ca984294dce07719c245788bd25ebd351ed1b6
https://blockchain.info/block/000000000000000002fd07858c4bd802af8f68ffb9ff1a4c97ef8be9d77e87ac

Tbh this happens all the time especially with the high amount of unconfirmed transactions, since the blocks are always full right now. If you look at the recent found blocks right now they are usually always 990+KB plus.

Also bitcoin mining is like a luck game. Sometimes there is no block for 2 hours and sometimes there will be two blocks in half a minute.

CoinCidental

legendary

Activity: 1316

Merit: 1000

Si vis pacem, para bellum

Quote from: chixka000 on November 19, 2016, 08:03:36 AM

This one is really unusual thing. As an update, It seems that the problem was already solved not that sure tho but the current unconfirmed blocks right now was almost 9k which 2k much lower than your post.

It is not unusual at all, sometimes they're are no blocks found in over an hour and then they find several at once or vice versa...
Its always been this way but you might not have noticed in the past as much as now since the blocks are basically full and there is a lot of transactions in the backlog when it happens now that wouldn't have been so noticeable in the past when the blocks were only 10-50% full (like the earlier few years)

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Quote from: rapazev on November 19, 2016, 03:42:25 PM

i'm not an expert, but when the nodes are updating they cant confirm transactions, can they?

Miners mine blocks and thats who we are talking about here. Miners would likely have a fallback server if the mining pool have a maintanence. It is unlikely that so many miners goes down and the blocks becomes delay because of that.

Cashew

sr. member

Activity: 391

Merit: 250

At least I learnt something today. I thought that there was exactly 10 minutes between each block but it seems it isn't the case.

p_linz

member

Activity: 113

Merit: 10

Quote from: nocryinginbtc on November 19, 2016, 04:10:30 PM

An insignificant statistical anomaly. This happens on all blockchains that I have seen.

this is not an statistical anomaly. i doesn't happen often but it is still normal and expected.

nocryinginbtc

jr. member

Activity: 33

Merit: 1

An insignificant statistical anomaly. This happens on all blockchains that I have seen.

rapazev

full member

Activity: 210

Merit: 100

i'm not an expert, but when the nodes are updating they cant confirm transactions, can they?

ranochigo

legendary

Activity: 3038

Merit: 4418

Crypto Swap Exchange

Varience. Bitcoin blocks are frequently affected by varience. Varience makes it such that Bitcoin blocks are not always at 10 minutes. The intervals from some blocks may vary from several seconds to hours. If the difficulty and the hashpower never changes, the average block time in the very long run will eventually be 10 minutes.

Coding Enthusiast

legendary

Activity: 1042

Merit: 2805

Bitcoin and C♯ Enthusiast

Quote from: OmegaStarScream on November 19, 2016, 07:45:39 AM

while the average should be 10 minutes .

There is no such rule. It just happens so that "usually" the "average" time between blocks are 10 minutes.

Quote

In the meantime , number of unconfirmed transaction is 11,000 and increasing... https://blockchain.info/unconfirmed-transactions

That is what happens when there is no block to contain the transactions!

Quote

I will assume It has nothing to do with SegWit and wait for a logical explanation .

Your assumption is right.
This happens rarely but it happens nonetheless. I am not going to try and explain why because I would like to leave that to the experts but it has something to do with difficulty.

Edit: Good to read if you are interested.
https://bitcoin.stackexchange.com/questions/855/what-keeps-the-average-block-time-at-10-minutes?rq=1
https://bitcoin.stackexchange.com/questions/3909/what-is-the-expected-time-until-the-next-block-is-found?rq=1

YIz

hero member

Activity: 686

Merit: 502

Quote from: OmegaStarScream on November 19, 2016, 07:45:39 AM

How come no blocks were found in the last 55 minutes (to be accurate) while the average should be 10 minutes . In the meantime , number of unconfirmed transaction is 11,000 and increasing... https://blockchain.info/unconfirmed-transactions I will assume It has nothing to do with SegWit and wait for a logical explanation .

EDIT : Two blocks was found (2 minutes between them) , not sure what's going on here.

https://blockchain.info/block/000000000000000001ed495dc3ca984294dce07719c245788bd25ebd351ed1b6
https://blockchain.info/block/000000000000000002fd07858c4bd802af8f68ffb9ff1a4c97ef8be9d77e87ac

It happens. sometimes blocks are found within 5 seconds and sometimes it takes a few hours. the average is 10 minutes assuming no major changes in hashrate between retargets.

chixka000

hero member

Activity: 910

Merit: 500

This one is really unusual thing. As an update, It seems that the problem was already solved not that sure tho but the current unconfirmed blocks right now was almost 9k which 2k much lower than your post.

OmegaStarScream

staff

Activity: 3500

Merit: 6152

How come no blocks were found in the last 55 minutes (to be accurate) while the average should be 10 minutes . In the meantime , number of unconfirmed transaction is 11,000 and increasing... https://blockchain.info/unconfirmed-transactions I will assume It has nothing to do with SegWit and wait for a logical explanation .

EDIT : Two blocks was found (2 minutes between them) , not sure what's going on here.

https://blockchain.info/block/000000000000000001ed495dc3ca984294dce07719c245788bd25ebd351ed1b6
https://blockchain.info/block/000000000000000002fd07858c4bd802af8f68ffb9ff1a4c97ef8be9d77e87ac

Topic: No blocks since in the last hour (Read 802 times)