What Is a "Shared Send" Transaction on a Blockchain?
What is a "shared send" transaction?
When people search for "blockchain shared send," the phrase almost always refers to a transaction that several unrelated users build together — combining their payments into one joint Bitcoin transaction instead of each sending a separate one. The general technique is known today as a coinjoin. This page explains the mechanics; it is not a recommendation for or against using any privacy tool.
The building blocks: inputs and outputs
A Bitcoin transaction is a bundle of inputs (coins being spent) and outputs (where those coins go). As the Bitcoin Developer Guide explains, nothing in the protocol says all of a transaction's inputs must come from one person — a single valid transaction can spend coins contributed by many different signers, with each signer authorizing only their own inputs. A shared or joint transaction simply takes advantage of that: several users each contribute an input and specify an output, everyone signs, and one combined transaction goes to the network.
Why anyone would do this
The motivation is privacy on a public ledger. Bitcoin's design, as laid out in the original whitepaper, keeps identities out of transactions but leaves the flow of coins fully public — and Nakamoto noted that multi-input transactions made by a single spender necessarily reveal that their inputs belonged to the same owner. Blockchain analysis leans heavily on that assumption: if several inputs are spent together, treat them as one wallet.
A jointly built transaction deliberately breaks that assumption. When the inputs belong to different people and the outputs are similarly sized, an outside observer looking at the ledger cannot reliably tell which output was paid by which input. Bitcoin Optech's coinjoin overview describes this class of transaction and lists a range of software projects that have implemented it — Sharedcoin, whose name echoes the "shared send" phrasing, appears among them.
What a shared transaction does and does not do
- It does blur the input-to-output mapping inside that one transaction, weakening the common-ownership assumption analysts rely on.
- It does not take coins off the blockchain. Every input and output is still recorded publicly and permanently, exactly like any other transaction — see our walkthrough of how a blockchain transaction works.
- It does not make anyone anonymous by itself. Amounts, timing, and what happens to the coins before and after the joint transaction all still leave public traces.
- It requires coordination. Participants must communicate to assemble the transaction, and each participant signs only their own inputs — an unsigned or half-signed joint transaction is invalid, so no one can spend anyone else's coins.
Trust and terminology
How the coordination happens varies by implementation. Some designs route the assembly through a coordinating server; others are peer-to-peer. The details differ project by project, which is why it is worth reading how any specific tool works before forming an opinion about it — the Optech topic page is a good index of the implementations and the research around them.
One more terminology note: "shared send" is unrelated to sharing in the social-media sense, and it is not a feature of a typical exchange account or hosted wallet. It is a construction at the raw-transaction level, which is why you mostly encounter the term in technical writing and older articles rather than in everyday wallet apps.
The compliance-shaped footnote
Combined transactions sit in an area that exchanges and regulators watch, and some services treat coins with a coinjoin history differently than others. Who oversees what in the U.S. crypto landscape is its own topic — covered in our guide to who regulates crypto in the U.S. — and anyone with real compliance questions should ask a qualified professional rather than a reference site.