Address Labels and Tags
MoneyFlow Lite attaches labels to addresses it recognises. Labels tell you what an address is, for example an exchange hot wallet, without leaving the trace.
The labels come from Bitquery's Address Labels API. The app shows them for the addresses in a trace. The API returns the same labels for any address, on any chain, in bulk. See Query labels with the API below.
Where labels appear
- Trace title: when the origin is a known address, its label shows next to the title, for example
bitkub-deposit. - Address details panel: under each address in the Addresses list.
- Transactions table: under the sender and receiver addresses.

In this Truebit exploit trace both receivers carry hacker-truebit-hacker plus one more label behind the +1 badge.

Label format
Labels are lower-case, hyphen-separated and follow the pattern <entity>-<type>. Labels seen in the app include:
| Label | Meaning |
|---|---|
bitmex-hot | BitMEX hot wallet |
bitmex-wallet | A BitMEX-controlled wallet |
bitmex-proof-of-reserves | Address BitMEX publishes in its proof of reserves |
bitkub-deposit | Deposit address belonging to the Bitkub exchange |
bitkub-proof-of-reserves | Address Bitkub publishes in its proof of reserves |
An address can carry several labels. The app shows the first one and a +n badge. Hover the badge to see the rest.
Each label has a type as well as a value. The app shows the value. The Address Labels API returns both, for example type cex-hot-wallet with value bitmex-hot.
What labels tell you in a trace
- Funds reaching a
-depositor-hotaddress have most likely entered an exchange. The exchange can identify the account holder. - Funds leaving a
-hotaddress are an exchange withdrawal. The sender is the exchange, not an individual. -proof-of-reservesaddresses are exchange treasury addresses.
Query labels with the API
Use the Address Labels API when you need labels outside a trace: to screen a list of deposit addresses, to check one counterparty before you trace it, or to enrich your own tooling. One query labels up to 100 addresses.
This query looks up one Ethereum address. Run it in the Bitquery IDE.
{
Metadata {
Labels(
where: {Address: {in: ["0x18e296053cbdf986196903e889b7dca7a73882f6"]}}
) {
Address
Chain
Label {
Type
Value
}
RecordedAt
}
}
}
The response identifies the address as a Bybit hot wallet on each chain where it is labelled:
{
"Metadata": {
"Labels": [
{
"Address": "0x18e296053cbdf986196903e889b7dca7a73882f6",
"Chain": "ethereum",
"Label": { "Type": "cex-hot-wallet", "Value": "bybit-hot-1" },
"RecordedAt": "2026-07-31T13:11:13Z"
},
{
"Address": "0x18e296053cbdf986196903e889b7dca7a73882f6",
"Chain": "bsc",
"Label": { "Type": "cex-hot-wallet", "Value": "bybit-hot" },
"RecordedAt": "2026-07-22T07:53:03Z"
}
]
}
}
Rules to remember:
- The
Addressfilter is mandatory. Pass EVM addresses in lowercase. - Up to 100 addresses per query. Bitcoin, Tron and Solana addresses work the same way.
- Labels can be corrected over time, so re-run a lookup to pick up changes.
The Address Labels API page covers batching, current-label views, exchange checks, frozen-address screening and the full list of label types.
Refresh labels
The crosshair icon in the toolbar above the panels schedules a fresh label scan for the addresses in the trace. The app confirms with Force scan task has been scheduled. Use it when a trace was created a while ago and new labels may exist.
Add your own tags
Every address, address group and edge has a New Tag button. Click it, type a tag and press Enter. Tags are your own notes, for example victim, mixer-suspect or a case number. They are stored with the MoneyFlow and show up in the Tags column of the MoneyFlows list.
Tags you add do not change Bitquery's labels and are not visible to other users unless you share the MoneyFlow.
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.