Transaction Propagation

Transaction propagation is how a newly broadcast Bitcoin transaction spreads across the peer-to-peer network. Starting from the originating node, the transaction ripples outward as each node validates it and relays it to its peers, until it has reached most of the network's mempools. There is no central queue; every node maintains its own mempool, and propagation is what keeps them roughly in sync.

The announce-then-fetch handshake

To avoid wasting bandwidth, nodes do not push full transactions blindly. A node first advertises a transaction by sending an inventory (INV) message containing only its hash. A peer that has not seen that hash replies with a GETDATA request, and only then does the sender transmit the full transaction in a TX message. Each node independently validates a transaction before relaying it onward, so invalid transactions die quickly instead of spreading.

Timing and privacy

Propagation across the network typically completes within seconds to tens of seconds. Bitcoin deliberately adds small randomized relay delays, a diffusion technique that makes it harder for an observer to trace a transaction back to its originating node, improving privacy. Because propagation is not instantaneous or perfectly uniform, two nodes can briefly hold conflicting views, which is exactly why unconfirmed payments carry double-spend risk.

See unconfirmed transaction and zero-confirmation transaction for what happens next.