Double Spending
Double spending is spending the same digital funds more than once. Preventing it without a central authority is the core problem blockchains solve, by keeping a shared ledger that records which funds have already been spent.
Digital money is just data, and data can be copied. Without a reliable record of which coins have already been spent, someone could send the same funds to two different recipients. Banks and payment processors prevent this by keeping a central ledger. Blockchains do it without one. Nodes check that every transaction spends only funds that are still unspent, and a consensus mechanism such as proof of work decides which of two conflicting transactions enters the shared ledger.
For example, Alice signs a payment to a merchant and, almost at the same moment, signs a second transaction sending the same coins back to her own address. Both may briefly sit in the mempool. Nodes reject any block that contains both, so the accepted chain can include only one of them at a time. If the merchant hands over goods before the payment is confirmed, the merchant could end up unpaid.
Confirmation greatly reduces this risk, but on proof-of-work chains it does not make a payment permanent. A chain reorganization can drop a confirmed transaction and confirm the conflicting one in its place. A 51% attack exploits this. An attacker controlling most of the hash power makes a payment, then builds a longer alternative chain in which that payment never happened. Each additional block makes reversal more costly and less likely, so finality is probabilistic rather than absolute. This is why recipients of large payments often wait for several confirmations. Other consensus designs handle finality differently.