Mixer Labels API
Find out whether an address is a mixer, or a wallet that used one. Bitquery labels more than 400,000 mixer addresses, mostly on Bitcoin, plus the Tornado Cash contracts on Ethereum and BNB Chain and the wallets that deposited to or withdrew from them.
ProductUsing this in production? See the Address Labels API page for plans, free trial and enterprise delivery options.
What it is
Label.Type | Meaning | Example Label.Value |
|---|---|---|
mixer | The mixer itself: a contract or service wallet | tornado-cash, tornado-cash-router, helix, bitcoin-fog, coinjoin |
mixer-user | Wallet that deposited to or received from a mixer | mixer-user-tornado-cash-depositor, mixer-user-tornado-cash-recipient |
privacy-protocol | Privacy service tag, often next to mixer | tornado-cash |
How to get it
Query the Metadata.Labels cube of the Address Labels API:
{
Metadata {
Labels(
where: {
Address: {in: [
"0xd90e2f925da726b50c4ed8d0fb90ad053324f31b",
"11121vmnDEVQVZDNpc4AdZiHbYiZvDGZdT",
"0x0001bbfdb7f5fc80fcb192e5544ce2c4b18f33df"
]}
Label: {Type: {in: ["mixer", "mixer-user"]}}
}
limitBy: {by: [Address, Chain, Label_Type], count: 1}
orderBy: {descending: RecordedAt}
) {
Address
Chain
Label {
Type
Value
}
RecordedAt
}
}
}
The response returns the Tornado Cash router as mixer, a Helix address on Bitcoin as mixer, and a wallet that received funds from Tornado Cash as mixer-user.
How it is derived
Bitquery's labelling pipeline compiles each label from many inputs and returns one finished result: a type, a value and the date it was recorded. Responses carry the label itself, not a per-label source reference.
Fields
| Field | Meaning |
|---|---|
Address | The address you queried |
Chain | Chain the label applies to |
Label.Type | mixer, mixer-user or privacy-protocol |
Label.Value | Mixer name, and for users the direction: depositor or recipient |
RecordedAt | When the label was added to Bitquery's label table |
Examples
Did this wallet withdraw from a mixer?
{
Metadata {
Labels(
where: {
Address: {is: "0x0001bbfdb7f5fc80fcb192e5544ce2c4b18f33df"}
Label: {Type: {is: "mixer-user"}, Value: {includes: "recipient"}}
}
limitBy: {by: [Chain, Label_Value], count: 1}
orderBy: {descending: RecordedAt}
) {
Chain
Label {
Value
}
}
}
}
Measure mixer exposure of a wallet
List the wallet's counterparties with the Transfers cube, label them here with Label.Type set to mixer, and sum the amounts sent to or received from the rows that match.
Pitfalls
mixerandmixer-userare different things. The first is the service. The second is a customer of it.- Coverage is uneven. Mixer service labels are dense on Bitcoin. On EVM chains they cover the Tornado Cash contracts.
- Using a mixer is not illegal everywhere. Treat the label as context for review.
Get the full dataset
The complete mixer and mixer-user lists are part of the Address Labels dataset on the Bitquery Data Store, for offline screening and research.
Frequently Asked Questions
How do I check if a wallet used Tornado Cash?
Query Metadata.Labels with the wallet address and Label Type set to mixer-user. The value says whether it was a depositor or a recipient.
Are Bitcoin mixers covered?
Yes. Most mixer labels are on Bitcoin, including Helix, Bitcoin Fog and CoinJoin addresses.
Related
Ready to run this in production?
Get an API key and run these queries in minutes, or talk to us about plans and enterprise delivery.