Chains where it is delegated
countCovered chains where the address's code is a delegation designator at the latest block.
Is this wallet delegated under EIP-7702 on any chain, and does its delegate contract sweep incoming funds?
Check one address on every EIP-7702 chain: delegated or not, to which contract, who set it and whether the code sweeps funds.
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.
One address on every covered chain: delegated or not, to what and since when.
Covered chains where the address's code is a delegation designator at the latest block.
Covered chains where the address's delegate matches known sweeper code by address or bytecode hash.
Authorizations recovered to this address that were signed with chain id zero, so they can be submitted on any chain.
ETH and major token balances the address holds on the chains where it is delegated, valued at oracle prices at the latest block.
Each covered chain with the delegate address, its label and class, the block and transaction that set it, the chain id signed and who paid the gas.
Every authorization recovered to the address, newest first: set, changed or cleared, with its nonce, chain id and transaction.
Known sweeper code across chains: funds swept, code families and where the funds land.
Funds forwarded out of accounts delegated to sweeper code in the last 30 days, valued at oracle prices at each sweep block.
Distinct runtime bytecode families the registry classifies as sweepers, counted across covered chains.
Value swept per day on each covered chain, so a new campaign shows when it starts and where.
The addresses that collect the most swept funds, with their code family, chains, accounts swept and value received.
An EIP-7702 delegation makes an ordinary wallet run a contract's code at its own address. This checker reads an address's code on every covered chain that supports EIP-7702 and answers directly: delegated or not, to which contract, set by which authorization and when. It also says whether the delegate is a known wallet implementation or code that sweeps funds out.
Delegation is how wallets add batching, gas sponsorship and passkeys, and it is also how attackers automate theft. A leaked key can be delegated to a sweeper that forwards every incoming payment to the attacker, so ETH sent to pay gas for rescuing the remaining tokens is gone in the same block. An authorization signed with chain id zero is valid on every chain at once, which is why the check reads each chain separately.
Every answer is read at the latest block, with the authorization transaction as its receipt. A clean result means no delegation is set right now; it says nothing about token approvals or other signatures, which the related checkers cover.
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 →Read from chain state and history
Enter the address. The checker reads its code on every covered chain: empty code means no delegation, and code that starts with the 0xef0100 designator means the account runs the delegate contract named after it. Each result links to the authorization that set it.
Sign a new authorization that delegates to the zero address and include it in a type 4 transaction; once it lands, the account's code is cleared on that chain. Wallets that support EIP-7702 offer this as switching back to a standard account. If someone else set the delegation with your key, the key itself is compromised and clearing it does not make the wallet safe again.
A delegate contract whose code forwards any ETH or tokens that reach the account to an address the attacker controls. Attackers holding a leaked key delegate the wallet to it so that gas money sent to rescue other assets is swept at once. Most sweepers are copies of a few code families, which is why bytecode matching finds them.
EIP-7702 lets a signer use chain id zero to make an authorization valid on every chain. Anyone holding that signature can submit it wherever the delegate address exists, so one phished signature can delegate the same wallet on several chains. The checker shows the chain id each authorization was signed for.
No. Funds stay at the same address, and the private key still controls the account. What changes is the code that runs when the account is called, so a malicious delegate can move funds whenever it is triggered, without a new signature.
How many accounts have delegated their code under EIP-7702, the contracts they point to and how much of it looks like sweeper scams.
Multi-chainEthereumBase+3What wallet drainers take each month, on which chains and through which signatures: approvals, permits, NFT listings and delegations.
Multi-chainEthereumEvery spender that can still move a wallet's tokens or NFTs, with the allowance, when it was granted and the transaction that set it.
Multi-chainCheck an address before you send or accept funds: direct flags and one-hop links to sanctioned, frozen, hacked or phishing addresses.
Multi-chainEthereumTron+1What an address is and who can act for it: wallet, contract, Safe or delegated account, its ENS name, deployer and labels with sources.
EthereumBaseArbitrum+3Thefts attributed to North Korea-linked groups, what their attributed wallets still hold and how the funds move across chains.
Multi-chainEthereumBitcoinStart 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.