user51782: In this question on StackOverflow, the OP is asking if there is a difference between distributed hash tables and blockchain. The answer to that question seems to indicate that there is no point of overlap between the two as they are for completely different purposes. However, I would like to clarify this point. 
To the best of my knowledge, blockchain is a peer-to-peer implementation, which means that the entire blockchain is stored in every peer. However, if there is a need to broadcast consensus of a particular transaction, there is still a need to look up the other peers in some kind of table of addresses. Am I correct? (My underlying question is: In a blockchain, would all nodes or peers get the information about successful transactions simultaneously? It doesn't seem likely to me, and I'm trying to understand the protocol for doing this broadcast in a simultaneous, or near simultaneous manner).

user52021: A blockchain needs a distributed hash table like a fish needs a bicycle.
The standard distributed hash table constructions achieve little to no particular robustness to attack for any actually useful definition of security, as a result they are not particularly useful for our applications.  Really, DHT just became a buzzword for "distributed" used most frequently by people who know only enough to be dangerous... until "blockchain" became a more popular buzzword for distributed.
What systems like Bitcoin do is distribute all the data to everyone. There is no need to look up routes or destinations, the system is a great big broadcast.  When a transaction comes in to a node, it offers it to each of its peers and if they don't already have it they'll request it.
It would be possible to do some other things-- though not generally the things in existent DHT systems because they don't generally achieve useful strong security properties-- but since validation in the Bitcoin style design requires everyone sees all the data it isn't particularly useful to avoid broadcasting it to all of them because they'll eventually need to see it all.

user48884: No. Peer discovery does not use a distributed hash table and cannot use a DHT. Once you are connected to the network, there is no need for you to find more peers to connect to (and most nodes have a limit of 8 anyways as that is Core's outbound connection limit).
The broadcasting of transactions and blocks themselves does not rely on the broadcaster to find all peers and send the data to each peer. Rather it simply sends the transaction or block to the peers it is connected to, and then those peers check the block and transaction, and if it is valid, they will send the block or transaction to their peers, and so on and so forth.

51782: <p>In <a href="https://stackoverflow.com/questions/26415908/whats-the-difference-between-distributed-hashtable-technology-and-the-bitcoin-b/36430343">this question</a> on StackOverflow, the OP is asking if there is a difference between distributed hash tables and blockchain. The answer to that question seems to indicate that there is no point of overlap between the two as they are for completely different purposes. However, I would like to clarify this point. </p>

<p>To the best of my knowledge, blockchain is a peer-to-peer implementation, which means that the entire blockchain is stored in every peer. However, if there is a need to broadcast consensus of a particular transaction, there is still a need to look up the other peers in some kind of table of addresses. Am I correct? (My underlying question is: In a blockchain, would all nodes or peers get the information about successful transactions simultaneously? It doesn't seem likely to me, and I'm trying to understand the protocol for doing this broadcast in a simultaneous, or near simultaneous manner).</p>
 52021: <p>A blockchain needs a distributed hash table like a fish needs a bicycle.</p>

<p>The standard distributed hash table constructions achieve little to no particular robustness to attack for any actually useful definition of security, as a result they are not particularly useful for our applications.  Really, DHT just became a buzzword for "distributed" used most frequently by people who know only enough to be dangerous... until "blockchain" became a more popular buzzword for distributed.</p>

<p>What systems like Bitcoin do is distribute all the data to everyone. There is no need to look up routes or destinations, the system is a great big broadcast.  When a transaction comes in to a node, it offers it to each of its peers and if they don't already have it they'll request it.</p>

<p>It would be possible to do some other things-- though not generally the things in existent DHT systems because they don't generally achieve useful strong security properties-- but since validation in the Bitcoin style design requires everyone sees all the data it isn't particularly useful to avoid broadcasting it to all of them because they'll eventually need to see it all.</p>
 48884: <p>No. Peer discovery does not use a distributed hash table and cannot use a DHT. Once you are connected to the network, there is no need for you to find more peers to connect to (and most nodes have a limit of 8 anyways as that is Core's outbound connection limit).</p>

<p>The broadcasting of transactions and blocks themselves does not rely on the broadcaster to find all peers and send the data to each peer. Rather it simply sends the transaction or block to the peers it is connected to, and then those peers check the block and transaction, and if it is valid, they will send the block or transaction to their peers, and so on and so forth.</p>
