| Token | Chain | Amount | Value |
|---|---|---|---|
| USDT | ethereum | 1.51B | $1.50B |
| BTC | bitcoin | 12K | $883.0M |
| MX | ethereum | 331.73M | $483.8M |
| USDC | ethereum | 313.44M | $313.4M |
| USD1 | ethereum | 138.92M | $138.6M |
| USDE | ethereum | 123.61M | $123.5M |
| ETH | ethereum | 43K | $94.9M |
| AUSDT | ethereum | 51.40M | $51.3M |
| SOL | solana | 368K | $32.7M |
| STETH | ethereum | 8,867 | $19.8M |
Not observed yet — the flow graph holds no observed links for this entity's 82 address(es) in the last 7 day(s) — the graph is self-building and fills as those addresses are visualised. No rows is not a quiet week.
| Address | Chain | Label | Claim |
|---|---|---|---|
| 0x51e3d44172868acc60d68ca99591ce4230bc75e0 | ethereum | MEXC.com | verified |
| 0x4982085c9e2f89f2ecb8131eca71afad896e89cb | ethereum | mexc.com | verified |
| 0xffb3118124cdaebd9095fa9a479895042018cac2 | ethereum | mexc.com | verified |
| 0x576b81f0c21edbc920ad63feeeb2b0736b018a58 | ethereum | MEXC.com 2 | verified |
| 0x2e8f79ad740de90dc5f5a9f0d8d9661a60725e64 | ethereum | Mexc.com 3 | verified |
| 0x0211f3cedbef3143223d3acf0e589747933e8527 | ethereum | mexc.com 2 | verified |
| 0x9642b23ed1e01df1092b92641051881a322f5d4e | ethereum | MEXC: Hot Wallet (0x964) | verified |
| 13uZyaPbt4rTwYQ8xWFySVUzWH3pk2P5c7 | bitcoin | exchange wallet (bitcoin) | community_tracked |
| bc1qrlsks7xe755m05zfreyjdxn34rypc4lnghtcwc | bitcoin | exchange wallet (bitcoin) | community_tracked |
| 35C2L1pCgwzBHNcDcVL1a5RuoefeWqyjAR | bitcoin | exchange wallet (bitcoin) | community_tracked |
Each address is a CLAIM with its level: verified (the entity or a disclosure says so), inferred (traced, corroborated), or community.
DeepGyre tracks MEXC by following the on-chain addresses attributed to the exchange — each one a claim with a stated level of evidence, listed in the table above. The tracked value is the sum of what those addresses hold right now: every position with a market price is priced, and positions no market can price are counted and listed separately instead of being valued at zero. An aggregator sweeps the addresses and refreshes the figures; a sweep that did not reach every address is labelled partial, and the page says so rather than presenting a floor as a total.
The value history is drawn from complete sweeps only. A sweep that missed addresses is excluded from the chart, because a lower total from an incomplete look would read as an outflow that never happened. Observed flows work the same way: transfers the flow graph actually saw over the last seven days, between the addresses it has reached — a floor, never the whole story.
Nothing here is a judgment of the exchange's health or solvency. On-chain balances show what the claimed addresses hold; they do not show liabilities, off-chain custody, or addresses nobody has attributed. When an attribution is wrong, the figures inherit the error — which is why every claim keeps its verification level and its source on the page.
No. It is the sum of the addresses attributed to it on chains DeepGyre scans. Custody held off-chain, unattributed wallets and liabilities are not on the chain and not on this page.
Two ways: the chain moved (deposits, withdrawals, price moves on held tokens) and the aggregator swept again. The history chart draws complete sweeps so a data gap never looks like an outflow.
Yes — the dashboard link opens the entity in the live app, where the flow graph, address list and alerts update as new blocks land.