Guides & Tutorials

How to Use Etherscan to Check and Revoke Token Approvals

Crypto wallet security illustration for a guide to reviewing token approvals.

When you use a decentralised exchange, NFT marketplace or other Ethereum application, you may approve a smart contract to move certain tokens from your wallet. That permission can remain in place after you have finished using the service. Etherscan’s Token Approval Checker provides a way to review those permissions and, when appropriate, revoke them.

This is a practical guide to the Ethereum version of the tool. You can inspect an address without connecting a wallet, then connect the wallet only if you decide to submit a revocation. The distinction matters: reviewing a public address is a read-only action, while revoking an approval changes blockchain state and costs a network fee.

Before you start

Have the public Ethereum address you want to review. If you plan to revoke an approval, you will also need access to the wallet that controls that address and enough ETH to pay the transaction fee. A desktop browser with your wallet extension installed is often the simplest way to follow the steps, although wallet connection options depend on the wallet you use.

  • Use the official Etherscan address: etherscan.io/tokenapprovalchecker.
  • Check that the browser shows the correct domain and a secure HTTPS connection.
  • Make sure you know which wallet account you intend to inspect.
  • Do not enter a recovery phrase, private key, wallet password or authentication code into Etherscan or any other website.

Step 1: Review approvals without connecting your wallet

Open the Token Approval Checker and enter the public wallet address in its search field. Submit the search. Etherscan’s help material describes this address lookup as a way to view approvals without first connecting the wallet. Your address is public blockchain information; it is not a password or a signing credential.

The results are grouped by token standard. Review the ERC-20, ERC-721 and ERC-1155 sections rather than looking only at the first list. ERC-20 approvals commonly relate to fungible tokens such as stablecoins. The other two standards cover NFTs, where an operator approval can have broader consequences than a single token allowance.

For each entry, pay attention to the token or collection, the approved spender, and the allowance or permission shown. A very large or unlimited ERC-20 allowance deserves attention, but the size alone does not prove that a contract is malicious. Some established applications request broad allowances to avoid asking for a new approval on every transaction. The important questions are whether you recognise the application, whether you still use it, and whether the permission is appropriate for that use.

Step 2: Check the spender before changing anything

Do not revoke an entry solely because its name is unfamiliar. Wallets and block explorers can display contract labels, but a familiar name is not a security guarantee and an unfamiliar address is not, by itself, proof of fraud.

Compare the spender address with the contract address published in the application’s own documentation. Navigate to that documentation independently rather than following an unsolicited message or an advertisement. You can also inspect the spender’s Etherscan contract page and transaction history. Verified source code can help with investigation, but verification does not certify that a contract is safe or that its owner cannot change its behaviour.

If you cannot establish what a spender belongs to, pause. It is safer to investigate first than to remove a permission that an application still needs or to connect your wallet to a lookalike approval site.

Step 3: Connect the correct wallet

Once you have decided that a particular permission is no longer needed, use the checker’s wallet connection option. Select the wallet account that matches the address you searched for. Confirm that the wallet is on Ethereum Mainnet and that the address shown by the wallet is the one you intend to manage.

Etherscan’s guidance notes that only the owner of the address can revoke its connected approvals. If the checker does not recognise the connected account, disconnect and check that you selected the correct account. Do not try to solve a connection problem by entering your recovery phrase or private key into the page.

Step 4: Revoke only the permission you have reviewed

Find the specific approval you want to remove and select its Revoke action. Your wallet should open a transaction confirmation. Read the request before approving it. Check the network, the account, the contract interaction and the estimated fee. The request should correspond to revoking the selected allowance or operator permission, not to transferring tokens, sending ETH or granting a new approval.

If the wallet displays an unexpected transaction, an unrelated message-signing request, a different network or details you cannot understand, reject it and stop. Do not approve a request simply because the checker says an approval is at risk.

When the transaction details match the revocation you intended, confirm it in your wallet. The revocation is an on-chain transaction, so it incurs a network fee. On Ethereum Mainnet that fee is paid in ETH, and the amount can vary with network conditions. Each revocation you submit is a separate transaction and may incur another fee.

Step 5: Confirm the result

Wait for the transaction to be confirmed. If your wallet or Etherscan provides a transaction hash, open that transaction on the official explorer and check its status. Return to the Token Approval Checker and refresh the results. The selected allowance should no longer be active, or the displayed amount should show that the permission has been reduced to zero.

If the transaction is pending, do not keep pressing Revoke. Check its status first. If it fails, the permission may still be active because the revocation was not successfully recorded. Resolve the wallet or network error before deciding whether another attempt is appropriate.

What revoking an approval does, and what it does not do

A successful revocation removes the relevant permission for future contract activity under that approval. It does not reverse transfers that have already happened, recover funds that have already been taken, or prove that the wallet is otherwise secure.

Revoking an approval is also different from disconnecting a website from your wallet. Disconnecting a dapp changes its connection to the wallet interface; revoking an allowance changes an on-chain permission that may allow a contract to move tokens. You may need to do both, depending on what you are trying to achieve. MetaMask explains the distinction in its guide to revoking smart contract allowances.

Take particular care with NFT operator approvals. An ERC-721 or ERC-1155 permission can allow an operator to manage all relevant tokens from a collection, rather than a single item. Revoke one only after checking which collection and operator it applies to.

Some token systems also use permit-style signatures or other authorisation methods that do not behave exactly like a standard on-chain ERC-20 allowance. MetaMask’s explanation of how token approvals work discusses this distinction. Treat Etherscan’s checker as a useful view of supported on-chain approvals, not as a complete audit of every signature, network or risk associated with a wallet.

Troubleshooting common problems

No approvals appear

First check that you entered the correct public address. Then confirm that you are using the explorer for the network on which the approval was made. The Etherscan checker is for Ethereum. MetaMask also points users to network-specific explorers such as BscScan and PolygonScan for those networks. An empty Ethereum result does not mean that the same wallet has no approvals elsewhere.

The Revoke option is unavailable

Check that the wallet is connected, that the selected account matches the address searched, and that the wallet is on the correct network. The address owner must authorise the revocation. If the account or network is wrong, switch to the correct one before continuing.

The transaction is pending or fails

Check the transaction status and the fee estimate in your wallet. Network congestion, an insufficient fee balance or a wallet connection problem can prevent a transaction from completing. Do not repeatedly submit the same action while an earlier transaction is still pending. If a transaction fails, verify whether the allowance remains active before taking any further step.

The approval still appears after confirmation

Refresh the checker after the transaction is confirmed and make sure you are looking at the same address and network. If the transaction succeeded but the entry remains, inspect the transaction details and the allowance again. Do not assume that a wallet notification alone proves the permission was removed.

A sensible routine, not a blanket reset

Reviewing approvals periodically is useful, especially after using applications you no longer intend to visit. But revoking every entry without understanding it is not a sound security policy. An active exchange, lending protocol or NFT marketplace may stop working as expected until you grant a new permission. Repeated approvals and revocations also create additional transaction fees.

Use the checker to identify permissions worth investigating, verify the spender independently, and remove only those you no longer need or trust. If you suspect that your recovery phrase or private key has been exposed, revoking allowances alone is not enough. Treat that as a wallet compromise and seek trusted wallet-provider guidance about protecting any remaining assets.

A hardware wallet can help protect private keys, but it cannot make an unsafe contract approval safe. For a broader look at hardware wallet trade-offs, see our Ledger vs Trezor security comparison.

Sources and further reading

Editorial note: This guide is based on desk research using Etherscan, MetaMask and OpenSea documentation checked on 19 November 2026. Big 5 Capital did not connect a wallet or submit a revocation transaction for this article. Interface labels may change, and readers should confirm the current transaction details in their own wallet before signing.

Tags:

1 comment

Leave a Reply

Your email address will not be published. Required fields are marked *