Public intelligence report · Elysium testnet
Unknown token (?)
0x2cae9bac2d5b500aaa860cce0a3a20d387f384d4
Looks healthy
Ascend score 90/100
Data through
Block 12,693,130
Scan window
347,279 → 12,693,130
Holders
0
Top 10 share
0.0%
Evidence ledger
What the scan found
Contract bytecode is present at 0x2cae9bac2d5b500aaa860cce0a3a20d387f384d4, but no ERC-20 Transfer events were found in the scanned range. This is a contract inspection, not a token-holder score.
Method: contract-inspection
No mint from the zero address was found in the scanned range, so the first minter is unknown. Try an earlier From block.
Method: first-minter
Only 0 wallets hold this token. Small holder counts are easy to fake and easy to move.
Method: holders
The 10 largest wallets hold 0.0% of supply. Supply is spread out.
Method: top-10
No linked wallet groups found. First tokens came from many different sources.
Method: linking
Interpretation
Read before interacting
This is an evidence report, not a guarantee of safety. A score reflects observed on-chain behavior in the selected window and can miss off-chain activity, unverified code, private permissions, or future changes.
Contract safety status: danger
- — An owner() function is exposed; privileged controls may exist.
- — The contract exposes pause state and currently reports paused=false.
- — Bytecode contains SELFDESTRUCT; review deployment and admin assumptions.
Permission surface
What the bytecode exposes
Selectors are evidence signals, not proof of behavior. A full verdict requires verified source code and transaction simulation.