BDHEX 0xb5a4…6699

BDHEX is the symbol of the PulseChain token at 0xb5a4f5fb22ff7fd733df0e34e3ddbbc560266699. Flagged: the scanner found 3 high-risk patterns in the contract code and a high-risk sign in where the supply or the liquidity went. Read the findings before trading. Reflection and tax tokens trip several of the code checks by design, so a Flagged contract means "read the findings", not proof of a scam. The supply sign is measured from the token's own transfers on the chain. As of 19 Oct 2026 12:07 UTC it traded at $0.0002147 (+404% over 24 hours), with $56.0K of liquidity and $191.1K traded in the last 24 hours. A token's name and symbol are chosen by whoever deployed it, not by DexDenom.com.

Contract address

0xb5a4f5fb22ff7fd733df0e34e3ddbbc560266699

Symbol (set by its deployer)

BDHEX

Name its contract reports (set by its deployer, not by DexDenom.com)

Black Diamond HEX

Price (USD)

$0.0002147

Change 5m / 1h / 24h

-1.7% / +50.6% / +404%

Market cap

$214.7K

Liquidity (TVL)

$56.0K

Volume 24h

$191.1K

Groups

Jungle (no group)

Scan

Flagged

Figures computed

19 Oct 2026 12:07 UTC

Scan: Flagged

What the scanner found in the code

• High: HIDDEN_ADMIN. Some functions are locked to an address that is not the owner() everyone can see - a second, hidden admin. Risk: The visible owner can renounce and the hidden one keeps the keys. Whatever those functions do (freeze, tax, mint) can still happen after 'renounce'. Harmless when: Rarely - a few frameworks use a separate operator role, but then it is documented and readable on chain.
• High: HIDDEN_BALANCE_WRITE. A function outside transfer / mint / burn can change wallet balances directly. Risk: The dev can take tokens out of any wallet, or conjure tokens into their own, without a trade and without you seeing a transfer. Harmless when: Reflection and reward tokens do exactly this on purpose (excludeAccount, reflect) - the balances are recomputed, not stolen. Check which it is before deciding.
• High: SILENT_SUPPLY. The total supply can be changed with no Transfer event - minting or burning that nothing announces. Risk: The dev can print supply and sell it into the pool; the first sign is the price falling. Harmless when: Rebase tokens change supply on purpose, but they normally emit something. Silence is the tell.
• Medium: TRANSFER_GATE. transfer() checks a per-address list before it lets a transfer through - a blacklist, whitelist or cooldown. Risk: The dev can stop you selling: add your wallet to the list, or hold everyone but themselves. This is how honeypots work - buys go through, sells do not. Harmless when: Anti-bot cooldowns at launch, or a max-wallet rule. Fine if it expires or is renounced; a gate the owner keeps forever is the honeypot switch.
• Medium: TRANSFER_SIDE_EFFECT. transfer() writes to storage that is not a balance or an allowance. Risk: Usually a tax, a counter or a last-trade timestamp - the plumbing taxes and cooldowns are built on. Not harmful by itself; it is where a changeable tax lives. Harmless when: Every tax and reflection token does this. Read the tax and whether the owner can change it.

What the supply did

• 99.99% of the LP tokens sit unlocked in a dev wallet - the liquidity can be pulled Risk: Whoever holds LP tokens can withdraw the pool's PLS at any moment - the classic rug pull. Nothing stops it but their word.

Its contract code is identical to 8 other tokens DexDenom.com has scanned; 8 of them lost most of their liquidity within 7 days of launch.

Scanned 14 Oct 2026 09:26 UTC.

Its deepest pools

Open the live page Full scan report PulseChain today

Figures come from PulseChain itself, read by DexDenom.com's own node: prices from each token's pools, liquidity (TVL) as the dollar value of what its pools hold, volume over the last 24 hours, market cap as the token's totalSupply() times its price. They are recomputed every 10 to 20 minutes. A scan reports what a token's code does and where its supply went; it is not financial advice, and "Warning" means nothing was found, not that a token is safe. The live, interactive version of everything here is on DexDenom.com. This page was built 19 Oct 2026 12:13 UTC.