BscScan: how to check a USDT transfer on BNB Chain

Open bscscan.com and paste the transfer hash into the search box — a 66-character string that starts with 0x. BscScan is made by the same team as Etherscan (it says so word for word in the footer of the site), so the transaction page reads exactly the same way: one single Status field with the values Success, Fail or Pending.

Don't go by the Block Confirmations counter the way you would in bitcoin: a block on BNB Chain lasts 0.45 seconds (measured 19.09.2026), so “174 confirmations” pile up in roughly a minute. Look at the Status field itself, not at the number beside it — that number says nothing about how safe the transfer is.

And here is one more trap peculiar to this network: BNB Chain has two different contracts that call themselves “Tether USD” with the ticker USDT, but with a different number of decimal places (verified 19.09.2026). The name of a token proves nothing — check the contract address shown on the transaction page.

The same developers as Etherscan — and it says so in the footer

In the footer of bscscan.com, as of 19.09.2026, there is the line ⛏ Built by Team Etherscan with a link to etherscan.io. This is not a resemblance of interfaces, it is a shared team, and there are two more proofs: the donation address is the same on both explorers, and the “API Documentation” item on BscScan leads to docs.etherscan.io, into the “Multichain API” section.

There is one practical conclusion: the fields of the transaction page are named the same and mean the same — Status, Value, Gas Price, Gas Limit & Usage by Txn, Transaction Fee. If you have already worked your way through Etherscan, you will not have to learn it all over again.

The differences are in the sections, not in how a transaction is read. BscScan has Validators instead of the Beacon Chain sections, the token tabs are called Top Tokens (BEP-20) and Token Transfers (BEP-20), and alongside them live the second-layer explorer opbnb.bscscan.com and the test network testnet.bscscan.com.

What the footer does not have is any mention of an owner of the network. All that stands there is “Powered By BNB Smart Chain” with a link to bnbchain.org: a pointer to the network, not to a proprietor. BscScan is neither a division of an exchange nor a part of BNB Chain. It is an explorer that the Etherscan team built for the BNB Smart Chain network.

The confirmation counter on BNB Chain means almost nothing

A live USDT transfer, captured from a BscScan page on 19.09.2026, showed 174 Block Confirmations about a minute after it was sent. Someone used to bitcoin reads that as “almost a day of confirmations”. On BNB Chain it is a minute.

The reason is the speed of the block. A measurement on 19.09.2026 across a thousand consecutive blocks: the average block is 0.450 seconds. That is how it has been since the Fermi hard fork, which went live on the main network on 14 January 2026 and cut the block from 0.75 to 0.45 seconds. Before that the Maxwell hard fork of 30.06.2025 cut it from 1.5 to 0.75.

The counter adds more than a hundred a minute, so there is no sense in comparing it with the number of confirmations on another network. The only field that answers the question “has the money gone or not” is Status. The value Success means the transfer has gone through, and the BEP-20 Tokens Transferred block on the same page confirms that the token really was sent across. How confirmations work in general is a separate write-up.

How long it takes for a transfer to become irreversible cannot be said exactly. The mechanism is described: a block counts as final once two thirds of the validators have voted. But the Fermi announcement itself gives no exact finality figure — you come across estimates of “about two blocks” and “about 0.65 seconds”. The order of magnitude is around a second, and that is all anyone can state honestly.

Three networks side by side: measured 19.09.2026

All the numbers are direct queries to nodes of the three networks on 19.09.2026. The “actual median” is what the wallets really paid; at the network base fee those same transfers would have come to $0.0128 on Ethereum and $0.0013 on BNB Chain.

The dollar figures live exactly until the next move of the rate, all the more on Ethereum: in that same sample some wallets paid the base fee and others a hundred and fifty times more for the same transfer in the same minute.

Two “Tether USD” tokens on one network — and both answer the same

This is the finding that makes it worth reading to the end. Direct calls to name(), symbol() and decimals() on two different BNB Chain contracts on 19.09.2026 returned the same name, the same ticker and a different number of decimal places.

The first is the one that circulates through the network en masse. Tellingly, BscScan itself labels it on the transaction page not as “Tether USD” but as Binance-Peg BSC-USD and (BUSD-T Stablecoin). Peg in that label means a pegged token, issued by someone other than Tether: that is precisely why the label is put there by the explorer and not by the contract — the name() field cannot be trusted.

That field is written by whoever deployed the contract. Anyone can deploy a contract on BNB Chain that answers “Tether USD” and “USDT”, and a wallet will obediently show that name on the screen. The only reliable identifier of a token is the contract address.

Hence the routine for checking a BEP20 transfer: on the page you look at the Interacted With (To) field — that is where the token's contract address stands — and compare it with the one you are expecting. A match means it is that token. No match means a different token with the same name is on the screen, whatever its label may promise.

How many contracts with the USDT ticker there are on the network in total, we do not know: we have no figure for it, and there is no point inventing one. Two specific addresses have been proved, and that is enough to stop believing the name.

Why a transfer costs a fraction of a cent

The network base fee on BNB Chain equals zero: baseFeePerGas = 0 in the latest blocks as of 19.09.2026, while the gas price the node suggests is 0.05 gwei. And the blocks are about half full at that, so the point is not an empty network but the way it is configured.

A live transfer from a BscScan page on 19.09.2026: Gas Limit & Usage by Txn: 207,128 | 51,603 (24.91%), Gas Price: 0.1 Gwei, Transaction Fee: 0.0000051603 BNB ($0.003959). The figures 0.05 and 0.1 gwei do not contradict each other: the first is the gas price the node suggests, the second is the one actually paid in this transfer.

That is less than half a cent of transfer fee. Actual median on 19.09.2026: $0.0027 on BNB Chain against $0.0385 on Ethereum. And that is more than five hundred times cheaper than a USDT transfer on TRON on the same date.

A caveat is obligatory: a cheap network does not mean a cheap withdrawal. The network fee and a service's rate are different money, and they live apart. We are an exchange service, and our rate has nothing to do with the price of gas on the network.

If the hash is not on BscScan

If the transfer is not there after a minute, there are usually three reasons. What has to be checked is the string itself, the network you chose and whether the transaction went out at all.

• It is not a hash — or it is a hash from another network. An order number in a wallet or a service and a transaction hash are different strings. A hash on BNB Chain is exactly 66 characters: 0x and 64 hexadecimal symbols. That is not a measurement but a property of the format: keccak256 gives 32 bytes, that is 64 characters written in hexadecimal, plus the prefix.
• On TRON the hash is the same 64 characters but without 0x, and that string is looked up in a TRON explorer. The correct length proves nothing on its own: Ethereum and BNB Chain use the same hash format, and a hash from the neighbouring network looks perfectly lawful here.
• The transfer went to a different network with the same address. A string of the form 0x… is identical on Ethereum, BNB Chain and several other networks, and a wallet will accept it as correct on any of them. The networks differ by their identifier: on Ethereum it is 1, on BNB Smart Chain it is 56 (verified 19.09.2026). What to do next is covered separately.
• The wallet signed the transfer but never broadcast it. No connection, the node refused — the transaction was signed locally and got into no block at all. The sign is simple: the hash is in the wallet's history, and the explorer has nothing under it. A hash on its own does not prove that the network ever learned about the transfer.

That an address lives on two networks at once is proved by that same donation address from the footer of both explorers. A direct query to the nodes on 19.09.2026: on Ethereum it holds 42.688948 ETH and 22,653.74 USDT, on BNB Chain 32.017013 BNB and 2,066.67 USDT. One string, different balances, two independent networks.

Once the transfer has been found and Status shows Success, the explorer has nothing left to answer. If the next step is an exchange, we have a separate direction for USDT on the TRON network: the network is stated in the direction itself, rather than picked at random in a wallet.

Quick answers

How many confirmations should you wait for on BNB Chain?

There is no point counting them. With a block of 0.45 seconds (measured 19.09.2026) the counter racks up more than a hundred a minute, and the number itself says nothing about safety. Look at the Status field: Success — the transfer has gone through. It becomes irreversible in about a second; there is no exact figure in the Fermi announcement.

Why does the Value field say 0 BNB?

Because what was sent was a token, not the coin of the network. Value shows the movement of BNB, and during a USDT transfer it is zero. Look for the token amount in the BEP-20 Tokens Transferred block.

If the block is not there, the token most likely did not go — but not always: the block is built from the Transfer event, and a contract may fail to emit it even though the balance has been debited. Then you ask the sender.

How do you tell real USDT from a token with the very same name?

By the contract address, not by the name. For the mass-market BEP-20 USDT there is one reference: 0x55d398326f99059fF775485246999027B3197955, and the explorer's label is Binance-Peg BSC-USD. It is against this string that the Interacted With (To) field is checked.

The second contract from the table above answers exactly the same — “Tether USD” and “USDT” (verified 19.09.2026) — and it is a different token. The name inside a contract is written by whoever deployed it, so what should be trusted is the address and the explorer's label.