Contract safety measurements on Ethereum, fetched live and rendered server-side. Each row names the endpoint it came from so you can check it yourself.
0x47accd13264d8f954105256faac8376ce6a55999 · view on Ethereum explorer
| Check | Value | Source |
|---|---|---|
| Honeypot simulation ran | NO | api.honeypot.is/v2/IsHoneypot (chainID=1) |
| Holders | 2,667 | api.honeypot.is/v2/IsHoneypot (chainID=1) |
| Source code verified | yes | api.gopluslabs.io/api/v1/token_security/1 |
| Mintable | no | api.gopluslabs.io/api/v1/token_security/1 |
| Owner can take back ownership | no | api.gopluslabs.io/api/v1/token_security/1 |
| Hidden owner | no | api.gopluslabs.io/api/v1/token_security/1 |
| Transfers pausable | no | api.gopluslabs.io/api/v1/token_security/1 |
| Blacklist function | no | api.gopluslabs.io/api/v1/token_security/1 |
| Proxy contract | no | api.gopluslabs.io/api/v1/token_security/1 |
| Creator holds | 1.18% | api.gopluslabs.io/api/v1/token_security/1 |
| Share | Classification | Source |
|---|---|---|
| LP holder 27.48% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x4c129c174e863be8160f42f7b11ec90066d5da0a |
| LP holder 27.48% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x12040dceec8d1622bc25a6e301654e456389c0aa |
| LP holder 17.42% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x500485ee637d5b4f39539a4e0e071e72fd314d87 |
| LP holder 16.01% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x48601a39e67d63f75e13fbd268494e3b80dd5fc3 |
| LP holder 9.16% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x583339c0e0d2530d9982732c7d2c31430b7f63f5 |
| LP holder 2.44% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x899720baa52df75c47a0c440cf5bf7818d796c4f |
"Unknown holder" means unknown, not unlocked. Our verified locker registry is deliberately empty: the first draft contained five locker addresses written from memory, and on-chain checks showed one was an empty wallet with no contract code and two could not be verified at all. A safety page that calls an empty wallet a locker is worse than one that admits the gap. The registry and its admission criteria.
The honeypot simulation could not run against this token. That usually means there is no meaningful liquidity to trade against yet — which is precisely the presale window where most losses happen. Treat "no honeypot detected" here as NO INFORMATION, not as good news.
This page states measurements, not a verdict. There is no score here on purpose: a number with its source beside it is something you can verify, and a score is something you have to trust. Checking many tokens at once? The same checks run as an API at Base Token Risk Scanner.