GC$GCATnew$12.5K+38.7%$熊new$23.1K-41.7%$Cagenew$21.4K+135.0%$大Anew$22.1K+239.0%$MESHnew$28.4K+59.6%GC$GCATnew$68.9K+685.0%$Cagenew$15.2K-63.1%GC$GCATnew$13.0K+47.8%MJ$MJnew$41.0K+201.0%DI$disnew$12.6K+39.7%犀牛$犀牛new$16.6K+92.0%$YAPOnew$49.3K+18.1%$‮熊new$2.0M+17.1%$SUIT Pennew$32.7K+72.8%MJ$MJnew$10.7K+23.3%TS$TSLAnew$88.2K+98.6%$蜜猴new$23.0K+38.0%$熊new$59.6K+492.0%$FILETnew$393K+800.0%$犀牛new$33.0K+285.0%$AKITAnew$270K+210.0%熊$熊new$84.0K+1543.0%TI$tilldienew$20.6K+127.0%熊$熊new$15.7K+84.0%$蜜猴new$102K+1068.0%$Darlanew$119K+182.0%$STRnew$224K+158.0%$StayDownnew$235K+171.0%$ANTSnew$94.6K+83.0%WE$WebAInew$11.9K+31.3%$REPnew$321K+269.0%TR$Trenchorsnew$51.4K+121.0%$VEIL$761K-41.5%$PAID$2.5M-8.9%$BATON$5.5M-0.9%$DARK$813K-19.9%$XTO$13.7M+10.7%$MISTAKE$14.8K-98.0%$HOOKED$1.1M-6.8%$E/ACC$412K-5.4%
Contract blueprint · 9 h ago

SNK on BNB Chain

0x9f478408a28637abaff8b18c60d0fd5207e5609b

Template-written 5 evidence items REA inspect-evm-interface (in WSL)
What this means for you

SNK on BNB Chain: no owner switches found among its 9 functions.E2E5

  • The contract has no owner() function, so there's no single owner wallet to check.E5

What it is

  • It's a token called Shin Kaze (SNK ).E3
  • Total supply: 1,000,000 tokens.E4
  • We read 9 functions from its public code with REA inspect-evm-interface (in WSL).E2E1

What the owner can do

No functions match known owner powers (mint, pause, block wallets, change fees or limits, open/close trading, replace the code).E2

Chain
BNB Chain
Address
0x9f478408a28637abaff8b18c60d0fd5207e5609b
Token
Shin Kaze (SNK )
Supply
1,000,000 tokens
Owner
no owner() function
Engine
REA inspect-evm-interface (in WSL)
All 9 functions
name()approve(address,uint256) · nonpayabletotalSupply()transferFrom(address,address,uint256) · nonpayabledecimals()balanceOf(address)symbol()transfer(address,uint256) · nonpayableallowance(address,address)

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

E1
3,263 bytes of contract code on BNB Chain
eth_getCode on BNB Chain · 0x9f478408a28637abaff8b18c60d0fd5207e5609b · sha256 31102ad605a1ec56…
E2
9 functions extracted with REA inspect-evm-interface (in WSL)
BNB Chain bytecode 0x9f478408… · “9 selectors” · REA inspect-evm-interface (in WSL)
E3
Token name/symbol: Shin Kaze (SNK )
eth_call name() / symbol() on BNB Chain · 0x9f478408a28637abaff8b18c60d0fd5207e5609b
E4
Total supply: 1,000,000 tokens
eth_call totalSupply() / decimals() on BNB Chain · 0x9f478408a28637abaff8b18c60d0fd5207e5609b
E5
No owner() function in the contract
BNB Chain bytecode · “no 0x8da5cb5b selector” · REA inspect-evm-interface (in WSL)

Limits

  • Powers are read from the contract's function list. A power hidden behind an unnamed function can't be explained, only counted.
  • Who holds a power is only checked through owner(). Roles, multisigs and proxy admins may hold powers too.
  • This describes what the code allows, not what anyone will do. It isn't financial advice.
  • This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id qoh21hNT.