{"id":392,"date":"2026-08-13T11:30:01","date_gmt":"2026-08-13T11:30:01","guid":{"rendered":"https:\/\/nownodes.io\/blog\/?p=392"},"modified":"2026-08-13T11:30:03","modified_gmt":"2026-08-13T11:30:03","slug":"how-to-retrieve-the-balance-of-a-bep-20-token","status":"publish","type":"post","link":"https:\/\/nownodes.io\/blog\/how-to-retrieve-the-balance-of-a-bep-20-token\/","title":{"rendered":"What Is a BNB Smart Chain (BSC) Address?"},"content":{"rendered":"\n

A BNB Smart Chain address is a 42-character string that starts with 0x<\/code> and points to something on the network \u2014 most often a wallet, sometimes a token contract. If you’ve ever copied a line like 0x55d3\u20267955<\/code> to receive USDT or connect to a dApp, you’ve already used a BSC address.<\/p>\n\n\n\n

This guide builds the topic up from the basics. We’ll start with what the address actually is, then cover why it matters, who uses it, and finally the developer-level stuff: finding a token’s contract address, checking balances in Node.js, and watching an address for incoming tokens in real time.<\/p>\n\n\n

What Is a BNB Smart Chain Address?<\/h2>\n\n\n

A BNB Smart Chain address is a unique identifier for an entity on the BSC network \u2014 a wallet, a token, or a smart contract. It’s written as a hexadecimal number: the prefix 0x<\/code> followed by 40 characters drawn from 0-9<\/code> and a-f<\/code>, which comes to 42 characters in total.<\/p>\n\n\n\n

Here’s the part that trips people up. Because BSC is compatible with the Ethereum Virtual Machine (EVM), a BNB address looks exactly like an Ethereum address \u2014 same length, same format. A valid BSC address looks like this:<\/p>\n\n\n\n

0x55d398326f99059fF775485246999027B3197955<\/code><\/pre>\n\n\n\n
Notice the mixed upper- and lowercase letters. That’s not random. The capitalization encodes a checksum defined by EIP-55<\/a>, which lets wallets catch typos before you send funds to the wrong place. An all-lowercase version of the same address is still valid \u2014 it just has no built-in error check. Either way, the address stays 42 characters long.<\/p>\n\n\n
Wallet Address vs Contract Address vs Transaction Hash<\/h2>\n\n\n
Not every 0x\u2026<\/code> string on BSC is a wallet. Three different things share the same hexadecimal look, and telling them apart saves a lot of confusion.<\/p>\n\n\n\n
Identifier<\/th>What it points to<\/th>Who controls it<\/th>Typical use<\/th><\/tr><\/thead>
Wallet address<\/strong><\/td>A user account (an EOA)<\/td>A private key you hold<\/td>Send and receive BNB and tokens<\/td><\/tr>
Contract address<\/strong><\/td>A deployed smart contract or token<\/td>Code, not a person<\/td>Identify a token; interact with a dApp<\/td><\/tr>
Transaction hash<\/strong><\/td>A single recorded transaction<\/td>Nobody \u2014 it’s a receipt<\/td>Look up the status of a transfer<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
A wallet address<\/strong> \u2014 an externally owned account \u2014 is what you share to receive funds. Whoever holds the matching private key controls it.<\/p>\n\n\n\n
A contract address<\/strong> is where a token or application lives on-chain. This is what people mean by a BNB token address or a BSC contract address: every BEP-20 token has its own, and that’s how your wallet knows which asset it’s dealing with. Native BNB is the exception \u2014 it belongs to the network itself and has no contract address.<\/p>\n\n\n\n
A transaction hash<\/strong> looks similar but isn’t an address at all. It’s a unique fingerprint for one transaction. You’d paste it into an explorer to confirm a transfer went through, as Indodax’s help center<\/a> walks through.<\/p>\n\n\n
Is BSC and BEP-20 the Same Thing?<\/h2>\n\n\n
\"\"<\/figure>\n\n\n\n
No \u2014 and this is worth getting straight. BSC is the blockchain; BEP-20 is the token standard that runs on it. BEP-20 defines the rules a token follows on BNB Smart Chain: how balances are stored, how transfers happen, how approvals work. It’s a direct extension of Ethereum’s ERC-20, which is why the two are almost interchangeable in code.<\/p>\n\n\n\n
So a “BEP-20 address” and a “BSC address” describe the same 42-character format. There used to be a second, incompatible format: BEP-2, which lived on the old BNB Beacon Chain. That chain was shut down in November 2024 as part of the Beacon Chain Fusion<\/a>, so BEP-2 is now retired and BEP-20 on BSC is the standard you’ll deal with.<\/p>\n\n\n\n
A concrete example makes this click. USDT on BSC is a BEP-20 token, and its verified contract address is 0x55d398326f99059fF775485246999027B3197955<\/code> \u2014 you can inspect it on BscScan<\/a>. One detail catches developers off guard: USDT on BSC uses 18 decimals, not the 6 decimals it uses on Ethereum. Always check a token’s decimals before doing math on its balance.<\/p>\n\n\n
Why You Need a BNB Smart Chain Address<\/h2>\n\n\n
An address is your point of contact with the whole network \u2014 nothing on BSC happens without one. It’s the destination people send BNB or tokens to, the account that signs transactions, and the identity dApps recognize when you connect a wallet.<\/p>\n\n\n\n
It’s also how you read the chain. Because BSC is a public ledger, any address’s balance and full history are visible to anyone. Paste an address into an explorer and you can see its BNB, its BEP-20 tokens, and every transfer it has ever made \u2014 which is exactly why so many people search for a BNB wallet address with balance to inspect what large holders are doing.<\/p>\n\n\n
Who Uses BSC Addresses<\/h2>\n\n\n
Pretty much everyone touching the network, but for different reasons:<\/p>\n\n\n\n