In briefOne node's local collection of accepted but unconfirmed transactions, which may differ from other nodes' collections.
Also referred to as: transaction pool · unconfirmed transactions · pending transaction
Full explanation
A node's local collection of unconfirmed transactions it currently accepts. Nodes can see, retain or remove different transactions, so there is no single global waiting room. Appearing in a mempool is not confirmation or a guarantee of later inclusion.
For exampleOne explorer may see your unconfirmed transaction while another node has not received it or has already removed it.
Common mistakeAssuming that absence from one mempool proves the payment was never broadcast or that a seen transaction must confirm.
One node's local collection of accepted but unconfirmed transactions, which may differ from other nodes' collections. A node's local collection of unconfirmed transactions it currently accepts. Nodes can see, retain or remove different transactions, so there is no single global waiting room. Appearing in a mempool is not confirmation or a guarantee of later inclusion.
What is a common mistake with Mempool?
Assuming that absence from one mempool proves the payment was never broadcast or that a seen transaction must confirm.
How is Mempool applied in practice?
One explorer may see your unconfirmed transaction while another node has not received it or has already removed it. You can explore this hands-on with our Explore network activity.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.