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.
What is known about who controls this address: an exchange, a protocol contract, a Safe, an ENS name or a flagged entity?
What an address is and who can act for it: wallet, contract, Safe or delegated account, its ENS name, deployer and labels with sources.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
What the address is, who can act for it and the labels that name it.
Plain account, contract, Safe, proxy or EIP-7702 delegated account, from the address's code at the latest block on the selected chain.
Label sets that name the address, each from a recorded source.
The date of the address's first transaction or first received transfer on any covered chain.
Covered chains where the address has sent a transaction, received funds or holds code.
Each label with its set, the source that supports it, the date it was added and the chains it applies to.
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.
Who the address deals with, summarised by label.
Distinct labelled addresses the address has sent funds to or received funds from on covered chains.
Share of the address's transferred value that went to or came from labelled exchange wallets.
Value exchanged with counterparties grouped by label type: exchange, protocol, bridge, fund, flagged or unlabelled.
The addresses it exchanged the most value with, their labels, the direction of flow and the first and last transfer.
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.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Chain data, with some off-chain sources
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.
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.
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.
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.
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.
Check an address before you send or accept funds: direct flags and one-hop links to sanctioned, frozen, hacked or phishing addresses.
Multi-chainEthereumTron+1Look up any EVM address and see what it holds on every covered chain, token by token, with first and last activity and no wallet to connect.
Multi-chainEthereumBase+4Inspect a Safe before trusting it: its signers, how many must sign, the modules and guards that can act on it and its recent changes.
Multi-chainEthereumBase+3Check one address on every EIP-7702 chain: delegated or not, to which contract, who set it and whether the code sweeps funds.
EthereumBaseOP Mainnet+5Every crypto address on the US sanctions list, with the entity behind it, what it holds now and the last time it moved funds.
BitcoinEthereumTron+4The Ethereum addresses holding the most ETH: what kind of address each one is, who it belongs to where known and how its balance moved.
EthereumStart free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.