Author

Topic: Block Arrival Time (Read 433 times)

copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
April 15, 2015, 01:49:36 PM
#5
While I was on Blockchain and Blocktrail I noticed a new block (352256) just came up, but it said the age was (around) 30 minutes ago.
I was thinking how was it mined 30 minutes ago but just showing up now.
On blocktrail https://www.blocktrail.com/BTC/block/0000000000000000149e57d3bb58654640746cd89aa364432a36d8db475b326c
It shows Block Time: Wednesday, April 15th 2015, 10:40:55 Arrival Time: Wednesday, April 15th 2015, 11:09:59
Did the miner mine the block but waited to broadcast it on the network?

The timestamp can be off a bit[1], it makes no sense to wait for broadcasting as this would only increase the likelyhood of someone else finding a block that also meets the target requirement. If we have two contesting blocks, yours might get orphaned, thus its important to broadcast it as soon as possible.

I think it takes some time until the block shows on all node and one the whole blockchain. I'm not a blockchain expert though so it might be because  of an other reason it ook so long to show on the blockchain.

Yes, it takes a bit, but nowhere near 30 minutes.

My understanding is that miners (or mining pools) have the ability to set their own timestamps.
The Bitcoin Protocol has encoded an allowable error of +/- in time, to a max of a 52 hour error.
This is so since it is not possible to have different miners systems all having the correct time, every time. Some lose time and etc.

The block was found recently and is in its proper order. It is just the broadcasted time-stamp (which the miners system says) that is off.

The timestamp is an easy and fast way to manipulate the block in a way that influences the hash, thus it is often manipulated on purpose in order to find a hash that matches the target criteria.


[1] >median(last 11 blocks) and https://en.bitcoin.it/wiki/Block_timestamp
sr. member
Activity: 490
Merit: 250
April 15, 2015, 01:48:36 PM
#4
My understanding is that miners (or mining pools) have the ability to set their own timestamps.
The Bitcoin Protocol has encoded an allowable error of +/- in time, to a max of a 5 hour error.
This is so since it is not possible to have different miners systems all having the correct time, every time. Some lose time and etc.

The block was found recently and is in its proper order. It is just the broadcasted time-stamp (which the miners system says) that is off.
This sounds like a better explanation than mine. Each miner has a different time so it takes sometime until the block shows on the blockchain.
legendary
Activity: 1092
Merit: 1001
April 15, 2015, 01:43:20 PM
#3
My understanding is that miners (or mining pools) have the ability to set their own timestamps.
The Bitcoin Protocol has encoded an allowable error of +/- in time, to a max of a 5 hour error.
This is so since it is not possible to have different miners systems all having the correct time, every time. Some lose time and etc.

The block was found recently and is in its proper order. It is just the broadcasted time-stamp (which the miners system says) that is off.
sr. member
Activity: 490
Merit: 250
April 15, 2015, 01:27:52 PM
#2
I think it takes some time until the block shows on all node and one the whole blockchain. I'm not a blockchain expert though so it might be because  of an other reason it ook so long to show on the blockchain.
member
Activity: 110
Merit: 10
April 15, 2015, 01:24:51 PM
#1
While I was on Blockchain and Blocktrail I noticed a new block (352256) just came up, but it said the age was (around) 30 minutes ago.
I was thinking how was it mined 30 minutes ago but just showing up now.
On blocktrail https://www.blocktrail.com/BTC/block/0000000000000000149e57d3bb58654640746cd89aa364432a36d8db475b326c
It shows Block Time: Wednesday, April 15th 2015, 10:40:55 Arrival Time: Wednesday, April 15th 2015, 11:09:59
Did the miner mine the block but waited to broadcast it on the network?
Jump to: