| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 26 Oct 2026 |
| Buy tax | 0% | Contract | 26 Oct 2026 |
| Sell tax | 0% | Contract | 26 Oct 2026 |
| Admin mint | Not present | Contract | 26 Oct 2026 |
| Transfers pausable | Not present | Contract | 26 Oct 2026 |
| Address blacklist | Not present | Contract | 26 Oct 2026 |
| Upgradeable proxy | No | Contract | 26 Oct 2026 |
| Source verified | Yes | Block explorer | 26 Oct 2026 |
| Liquidity locked | 100%, end date unknown | LP holders · PinkLock02 | 26 Oct 2026 |
| Holders | 0 | Token contract | 26 Oct 2026 |
| Deployed by | 0x98527c…ad4084 |
This automated check scanned the Hellhound (HELL) contract on BSC and found no honeypot behaviour: a simulated transfer went through, meaning holders were able to sell at the time of the check. Buy and sell tax were both read at 0% from the contract code. No admin mint function was detected, which means the contract does not currently contain a built-in way for the owner to create new tokens and dilute holders. No pause function was found, so the owner does not appear able to freeze transfers for everyone. No blacklist function was found either, which would otherwise let an owner block specific addresses from trading. The contract is not an upgradeable proxy, meaning its logic cannot be swapped out later for different rules. Source code is verified on the block explorer, so the logic reviewed here matches what is publicly visible. Liquidity is reported as 100% locked via PinkLock, though the unlock date could not be determined — a lock with no visible end date is harder to rely on than one with a confirmed, distant expiry.
None of this tells you who controls the project, how tokens are distributed, or what the team intends to do with it. The holder count reads as zero, which on its own is unusual and may reflect indexing lag, a very new deployment, or very limited distribution so far — it is not evidence of activity or lack of it. This check only reads contract mechanics as they existed at the time of scanning; it does not assess the team behind the token, its tokenomics, marketing claims, roadmap, or legal status, and it cannot predict whether any of these contract permissions could change through a future upgrade or redeployment, or whether off-chain arrangements exist that aren't visible on-chain.
Before putting any money toward this or any token, it's worth independently verifying the liquidity lock directly on PinkLock to see the actual unlock date and locked amount, checking how tokens are distributed among current holders (a small number of wallets holding most of the supply is a common concentration risk even when the contract itself looks clean), looking at the contract owner address to see if ownership has been renounced or still rests with a wallet that could interact with the contract in ways not flagged here, and searching for the project's community channels, audits, or prior history. Findings on this page reflect only what automated analysis detected on the date of the check and can change if the contract, its liquidity, or its ownership change afterward.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 12 points out of 100.
The other 88 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.