Honeypot Token Checker: Can This Token Be Sold?
A simulated buy and sell at the latest block shows whether a token can be sold and what it really charges in buy and sell tax.
Multi-chainEthereumBNB Chain+1Which powers does this token contract still keep: minting, blacklisting, pausing, fee changes or upgrades?
The powers a token contract still keeps, from minting and blacklisting to pausing, fee changes and upgrades, read from the contract.
The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
One row One row per token contract per chain, read at the latest blockSorted by Top 10 holders, highest first
| Token | Chain | Owner | Ownership renounced | Can mint | Can blacklist | Can pause | Fee control | Upgradeable | Top 10 holders | Receipt |
|---|---|---|---|---|---|---|---|---|---|---|
Filter by Chain, Ownership renounced, Can mint, Upgradeable.
Many token losses come from powers the contract never gave up: an owner who can mint new supply, blacklist holders, pause transfers, raise fees or swap in new code. This table reads those powers from each token's bytecode and storage, so a reader can see what the deployer can still do before buying, listing or integrating a token.
Each row shows whether ownership is renounced, whether the contract sits behind an upgradeable proxy and who controls it, which privileged functions exist and how concentrated the top holders are. A clean row is not a promise of safety: it lists what the code allows today and links the reads that show it.
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
No on-chain check can prove a token is safe. What can be read is what the contract allows: whether someone can still mint, blacklist, pause, change fees or upgrade it, and how concentrated its holders are. This table shows those facts with their reads and leaves the judgement to the reader.
Renouncing moves a contract's owner role to the zero address, so owner-only functions can no longer be called. It only helps if no other role or proxy admin can still change the contract, which is why the table checks both.
A mint function lets its controller create new tokens at will, which can dilute every holder or supply tokens to sell into the pool. Many legitimate tokens have one under a governance or multisig owner, so the table shows who controls it.
A blacklist function lets the owner block chosen addresses from sending or receiving the token. Stablecoins use one to freeze stolen funds; in a new token it can stop buyers from selling, which is how many honeypots work.
An upgradeable token sits behind a proxy that forwards calls to an implementation contract, and its admin can point the proxy at new code. The token's rules can then change completely, so the table names the admin and whether it is a single key, a multisig or a timelock.
A simulated buy and sell at the latest block shows whether a token can be sold and what it really charges in buy and sell tax.
Multi-chainEthereumBNB Chain+1Newly launched tokens whose liquidity was pulled or whose deployer sold out within days, counted per chain and day from pool events.
Multi-chainSolanaBase+2Every 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-chainImplementation, admin, owner and multisig signer changes on major protocol contracts, and the upgrades already queued in timelocks.
Multi-chainEthereumTokens created in the last 24 hours that opened a DEX pool, with chain, launchpad, deployer, starting liquidity and holders.
Multi-chainSolanaBase+2Bitcoin held in outputs whose public keys are already visible on-chain, split by script type and tracked day by day.
BitcoinStart 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.