<p>If I understand your question, your latency compared to blockchain.info is motivated to the blockchain.ifo use the node distributed to the world and you have only the one node.</p>

<p>I have read <a href="https://arxiv.org/pdf/1709.02489.pdf" rel="nofollow noreferrer">this reasearch</a> where write this</p>

<blockquote>
  <p>In  any  peer-to-peer  system,  dierent  nodes  will  receive  thesame data at different times.  Blockchain.info uses a geographi-﻿cally distributed set of nodes to obtain relatively accurate times-tamps.   BlockSci is a single-node system,  so its timestamps in-evitably lag those of blockchain.info. Based on 2 weeks of mempooldata recorded by our AWS node in theus-east-1ddata center, wefound that our timestamps lag blockchain.info’s timestamps byan average of 16 seconds and a standard deviation of 4 seconds.Any BlockSci user can perform a similar measurement and apply auniform correction to eliminate the average lag, but of course the﻿variance will remain.</p>
</blockquote>

CC BY-SA 4.0
2019-10-25T18:30:34.807Z
Okay I understand, I will read the research, thank you !
Whitey
CC BY-SA 4.0
2019-10-23T13:39:28.237Z
2019-10-23T13:39:28.237Z
vincenzopalazzo
<p>I am on Ubuntu 16.04, with the latest version of Bitcoin Core, synced and working.</p>

<p>I would like to know why is there a little delay of approximately 1 sec, sometimes more, before a received transaction appear on the console when we run for instance <code>bitcoind -printoconsole</code>, if I check the tx on blockchain.com for instance, I can see that the transaction were received 1 or 2 sec before I even see it on my node, why is there a delay ? I have try on another ubuntu server with a super fast connection and it's the same thing. By the way, it's the same thing when I send a Tx, it's submitted and appear on the network 1-2 secs after.</p>

<p>So my question is why is there such a delay even on a node ? Is it possible to reduce it ?</p>

<p>I have already asked the same question on the bitcoin repo on github and someone told me that it is an intentional delay against attackers, but what I don't understand is why blockchain has access to it before node ? If they can it mean that we can too right ? </p>

<p>Just like when few years ago and even months, some brainwallet were swipped within milliseconds. </p>

<p>Thanks in advance !</p>

<bitcoin-core><transactions><bitcoind><unconfirmed-transactions>
Receive/send Transactions latency
Whitey
# Receive/send Transactions latency

(Asked by: username_0 on 2019-10-23)

I am on Ubuntu 16.04, with the latest version of Bitcoin Core, synced and working.

I would like to know why is there a little delay of approximately 1 sec, sometimes more, before a received transaction appear on the console when we run for instance `bitcoind -printoconsole`, if I check the tx on blockchain.com for instance, I can see that the transaction were received 1 or 2 sec before I even see it on my node, why is there a delay ? I have try on another ubuntu server with a super fast connection and it's the same thing. By the way, it's the same thing when I send a Tx, it's submitted and appear on the network 1-2 secs after.

So my question is why is there such a delay even on a node ? Is it possible to reduce it ?

I have already asked the same question on the bitcoin repo on github and someone told me that it is an intentional delay against attackers, but what I don't understand is why blockchain has access to it before node ? If they can it mean that we can too right ?

Just like when few years ago and even months, some brainwallet were swipped within milliseconds.

Thanks in advance !

**Tags:** bitcoin-core, transactions, bitcoind, unconfirmed-transactions


---

## 1 answers

### Answer by username_1 on 2019-10-23. Score: 0 | Accepted answer

If I understand your question, your latency compared to blockchain.info is motivated to the blockchain.ifo use the node distributed to the world and you have only the one node.

I have read [this reasearch](https://arxiv.org/pdf/1709.02489.pdf) where write this

> In any peer-to-peer system, dierent nodes will receive thesame data at different times. Blockchain.info uses a geographi-﻿cally distributed set of nodes to obtain relatively accurate times-tamps. BlockSci is a single-node system, so its timestamps in-evitably lag those of blockchain.info. Based on 2 weeks of mempooldata recorded by our AWS node in theus-east-1ddata center, wefound that our timestamps lag blockchain.info’s timestamps byan average of 16 seconds and a standard deviation of 4 seconds.Any BlockSci user can perform a similar measurement and apply auniform correction to eliminate the average lag, but of course the﻿variance will remain.

> **Comments:**
> **username_0**: Okay I understand, I will read the research, thank you !  

---

