How long does crypto mixing take?
There is no universal duration. A quoted time is meaningful only when it names the start event, confirmation requirement, selected or imposed delay, queue and liquidity assumptions, payout rule, number of outputs, timeout behavior, and completion event.
A payout broadcast is not the same as a destination confirmation. An address being generated is not the same as an input being accepted. Compare like-for-like events before comparing times.
Start-to-finish event timeline
Quote or address
Terms may be displayed, but no network transaction has necessarily started.
Input broadcast
The source wallet submits a transaction; acceptance and confirmation are separate events.
Input accepted
A route may wait for a stated confirmation count or another review condition.
Delay or processing
Selected delay, queue, liquidity, screening, and split-output rules may apply.
Payout complete
Define whether this means broadcast, every output sent, or destination confirmation.
Use events, not adjectives
“Fast” and “instant” have no testable meaning until the start, end, assumptions, percentile or range, and failure cases are stated.
Selected delay and operational delay are different
- Confirmation delay
- Time for the input or output transaction to reach a stated confirmation condition on its network.
- Selected delay
- A user-configured or route-defined waiting period. Its purpose does not prove a privacy result.
- Queue or liquidity delay
- Time caused by processing order, asset availability, payout construction, or operational constraints.
- Review or exception delay
- Time added by screening, a route mismatch, manual review, timeout handling, or a recovery request.
A longer delay can change timing correlation, but it also extends custody exposure and uncertainty. It does not guarantee that amounts, counterparties, later deposits, or other signals become unlinkable.
Delay and payout-state matrix
Input not yet accepted
Confirm whether the transaction is merely broadcast, below a confirmation threshold, expired, or sent through a mismatched asset or network.
Accepted, payout not started
Ask which delay, queue, liquidity, screening, or batching condition applies and where that condition is documented.
Payout transaction exists
Preserve each transaction identifier and distinguish broadcast from confirmation at the destination.
Some outputs are missing
Record the amount and time for every output, added fees, timeout rules, and the stated recovery path.
No expected state change
Preserve the exact domain, quote, receipt, timestamps, transaction identifiers, and support messages. Do not send more funds to unlock a route.
End event is observable
Use a narrow event such as every payout reaching the documented confirmation condition. This proves completion, not privacy or safety.
Timing assumptions worksheet
Record the source and observation date beside every operator-specific assumption. Missing timing evidence remains Not verified, not zero minutes.
Timing uncertainty affects custody exposure and total route cost.
Start mixing