Contract blueprint · 27 Oct 2026

BIN💰 on BNB Chain

0xb795e37e5b27e86ea9c1fea4cd7876934425283d

Template-written 7 evidence items REA inspect-evm-interface (in WSL)

What this means for you

BIN💰 on BNB Chain: no owner switches found among its 18 functions.E2 E5

Ownership is given up (renounced), so owner-only switches are locked.E5
6 functions that change state have no public name, so we can't say what they do.E7

What it is

It's a token called BinanceBSC💰 (BIN💰).E3
Total supply: 1,000,000,000 tokens.E4
Besides the standard token functions it has renounceOwnership, owner and transferOwnership.E2
We read 18 functions from its public code with REA inspect-evm-interface (in WSL).E2 E1

What the owner can do

Transfer ownership

info

Ownership can be handed to another wallet or given up (renounced).E6 E5

renounceOwnership()transferOwnership(address)

6 state-changing functions have no public name: 0x16503bfe 0x3a3bd434 0x44b28d59 0x4a387bef 0x8c1437cf 0xb0fc29e6 E7

Chain: BNB Chain
Address: 0xb795e37e5b27e86ea9c1fea4cd7876934425283d
Token: BinanceBSC💰 (BIN💰)
Supply: 1,000,000,000 tokens
Owner: 0x0000000000000000000000000000000000000000
Engine: REA inspect-evm-interface (in WSL)

All 18 functions

name()approve(address,uint256) · nonpayable0x16503bfe(uint256[],uint256) · nonpayabletotalSupply()transferFrom(address,address,uint256) · nonpayabledecimals()0x3a3bd434(uint256[]) · nonpayable0x44b28d59() · nonpayable0x4a387bef(address) · nonpayablebalanceOf(address)renounceOwnership() · nonpayable0x8c1437cf(address,bytes,uint256,uint256) · nonpayableowner()symbol()transfer(address,uint256) · nonpayable0xb0fc29e6(address,uint256) · nonpayableallowance(address,address)transferOwnership(address) · nonpayable

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.

3,805 bytes of contract code on BNB Chain

eth_getCode on BNB Chain · 0xb795e37e5b27e86ea9c1fea4cd7876934425283d · sha256 8846ca3cfaff2de3…

18 functions extracted with REA inspect-evm-interface (in WSL)

BNB Chain bytecode 0xb795e37e… · “18 selectors” · REA inspect-evm-interface (in WSL)

Token name/symbol: BinanceBSC💰 (BIN💰)

eth_call name() / symbol() on BNB Chain · 0xb795e37e5b27e86ea9c1fea4cd7876934425283d

Total supply: 1,000,000,000 tokens

eth_call totalSupply() / decimals() on BNB Chain · 0xb795e37e5b27e86ea9c1fea4cd7876934425283d

owner() returns 0x0000000000000000000000000000000000000000 (zero/dead address: renounced)

eth_call owner() on BNB Chain · 0xb795e37e5b27e86ea9c1fea4cd7876934425283d

Owner switch 'Transfer ownership': renounceOwnership(), transferOwnership(address)

Ownership can be handed to another wallet or given up (renounced).

BNB Chain bytecode 0xb795e37e… · “renounceOwnership(), transferOwnership(address)” · REA inspect-evm-interface (in WSL)

6 state-changing function(s) with no public name

BNB Chain bytecode · “0x16503bfe, 0x3a3bd434, 0x44b28d59, 0x4a387bef” · 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 6vYhRFFr.