# Address Label Lookup: Who Controls This Wallet? > Look up any EVM address: whether it is a wallet, contract, Safe or delegated account, its ENS name, deployer, owners and public labels, each with a source. Markdown copy of https://voltfincrypto.com/apps/address-label-lookup **Question:** What is known about who controls this address: an exchange, a protocol contract, a Safe, an ENS name or a flagged entity? - Kind: Dashboard in Voltfin Vantage - Topic: [Wallets and whales](https://voltfincrypto.com/topics/wallets) - Chains: Ethereum, Base, Arbitrum, OP Mainnet, BNB Chain, Polygon - Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is. A blockchain address carries no name, but it carries evidence. Its code says whether it is a plain wallet, a contract, a Safe or a wallet delegated under EIP-7702; contracts record who deployed them and who can upgrade them; and many addresses have public labels, from exchange reserve lists to protocol deployments. This lookup reads all of it for one address and shows what each piece of evidence says. Labels are shown with their sources and never invented: an address no one has identified is shown as unlabelled. An ENS name is shown only when the address chose it as its primary name and the name points back, so a name someone aimed at the address without its consent does not count. Counterparties are summarised by label, so a wallet that mostly deals with one exchange reads differently from a contract many people use. ## Blueprint ### Identity What the address is, who can act for it and the labels that name it. - **Account type**: Plain account, contract, Safe, proxy or EIP-7702 delegated account, from the address's code at the latest block on the selected chain. - **Labels found** (count): Label sets that name the address, each from a recorded source. - **First seen** (date): The date of the address's first transaction or first received transfer on any covered chain. - **Chains with activity** (count): Covered chains where the address has sent a transaction, received funds or holds code. - **Labels and their sources**: Each label with its set, the source that supports it, the date it was added and the chains it applies to. - **Who can act for it**: For a Safe its owners and threshold, for a proxy its admin and implementation, for a contract its deployer and owner and for a delegated account its delegate. ### Counterparties Who the address deals with, summarised by label. - **Labelled counterparties** (count): Distinct labelled addresses the address has sent funds to or received funds from on covered chains. - **Value with exchanges** (%): Share of the address's transferred value that went to or came from labelled exchange wallets. - **Counterparties by label type** (USD): Value exchanged with counterparties grouped by label type: exchange, protocol, bridge, fund, flagged or unlabelled. - **Top counterparties**: The addresses it exchanged the most value with, their labels, the direction of flow and the first and last transfer. Filters: Address or ENS name (Any EVM address or .eth name); Chain (Every covered chain). ## How it will be measured - Account type comes from eth_getCode at the latest block: empty code is a plain account, the 0xef0100 designator is an EIP-7702 delegation and contract code is classified further by known patterns such as Safe and EIP-1967 proxies. - An ENS name is shown when the address's reverse record names it and the name's forward record resolves back to the same address. - Control is read from the contract: owner() where it exists, a Safe's getOwners() and getThreshold() and a proxy's admin and implementation slots, with the deployer and creation transaction from traces. - Labels come from reviewed sets (exchange-published wallets, protocol deployments, the OFAC list and the incident registry), each with its source and date; deposit addresses are labelled from their sweeps into an exchange wallet. ## Data it needs - `address_labels` (to build): Labels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers. - `token_holders_snapshot` (to build): Holder counts, top holders and concentration shares of registry tokens at a pinned block, with contract and exchange labels. - `native_prices_daily` (to build): Reference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time. - Source: eth_getCode of the address on each covered chain at the latest block - Source: ENS reverse records and forward resolution on Ethereum, read through the ENS registry and resolvers - Source: owner(), getOwners(), getThreshold() and the EIP-1967 admin and implementation slots where they apply - Source: Contract creation transactions and deployers from traces - Source: Exchange-published wallets, protocol deployment lists, the OFAC SDN list and the incident registry (off-chain labels with sources) ## Questions ### Can you find out who owns a crypto wallet? Not from the chain alone. A plain wallet is controlled by whoever holds its key. What can be known comes from evidence: an exchange publishing its addresses, a protocol listing its contracts, an ENS name the owner chose or patterns such as deposits swept into an exchange. The lookup shows each piece with its source. ### How can I tell if an address is a contract or a wallet? Read its code. A plain wallet has none, a contract has bytecode and a wallet delegated under EIP-7702 has a short designator pointing at a contract. The lookup reads this on each covered chain, since the same address can be a contract on one chain and empty on another. ### What is an ENS primary name? The name an address has chosen to be known by, set in its ENS reverse record. Because anyone can point their own name at any address, a name only belongs to an address when the reverse record and the forward record agree. ### What does it mean if an address is a Safe? It is a multisig account: its transactions need signatures from a set number of its owners. The lookup lists the owners and the threshold read from the Safe itself, which says who can move its funds. ### Is a label proof of who controls an address? No. A label is evidence with a source, such as an exchange's published list or a protocol's documentation. Labels can be wrong or out of date, so each one shows where it came from and when it was added. ## Glossary - **EOA**: An externally owned account: a plain address controlled by a private key, with no contract code of its own. - **Primary name**: The ENS name an address has set in its reverse record, trusted when the name's forward record resolves back to that address. - **Deposit address**: An address an exchange assigns to one customer, which forwards incoming funds to the exchange's hot wallet. ## Related apps - [Crypto Address Checker: Flagged, Sanctioned or Hacked](https://voltfincrypto.com/apps/crypto-address-checker) - [Wallet Balance Checker: Every EVM Chain in One View](https://voltfincrypto.com/apps/wallet-balance-checker) - [Safe Multisig Checker: Owners, Threshold and Modules](https://voltfincrypto.com/apps/safe-multisig-checker) - [EIP-7702 Delegation Checker: Is Your Wallet Delegated?](https://voltfincrypto.com/apps/eip-7702-delegation-checker) - [OFAC Sanctioned Crypto Addresses: Balances and Activity](https://voltfincrypto.com/apps/ofac-sanctioned-crypto-addresses) - [ETH Rich List: Top Ethereum Addresses by Balance](https://voltfincrypto.com/apps/eth-rich-list) Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F