Fake 0 Token Transaction – Understanding the Fake 0 Token Transaction Phenomenon on BSC

Note: This StackExchange is focused on Ethereum and the question is BSC specific, therefore off-topic.

Regarding your question: MetaMask uses information about the contracts and existing abis to decode the transaction data. If you deploy a new contract on a network that MetaMask does not support for transaction decoding you will see this message.

Transaction decoding just shows more information on the hex data to make sure that the user knows what they are signing. Even if this is not available on a specific network you can still execute the transaction.

If you already submitted a transaction and it failed, then you should share the transaction hash to that transaction so that it is possible to look into it. If you want to get support on this StackExchange I would also recommend to use one of the official Ethereum test networks (e.g. Rinkeby, Goerli, Ropsten or Kovan)

No, nothing except a random number is used to generate a private key. There is an extremely small chance that your private key would map to the same address as another private key, and there is also an extremely small chance that someone would randomly generate a private key you currently control. The chances are so small that these scenarios are for all practical purposes assumed to be impossible.

The address for your private key is the same on all of these networks because you are using the same private key, and they are using the exact same signature scheme that Ethereum is - so, your private key maps to the same public key, and the public key is used to generate the address.

You can read more on the chances of private key collissions here:

Ethereum addresses are 160 bit hashes, meaning there are 2^160 possible hashes. Per the birthday problem, the chance of a collision rises to 50% when there are about 2^80 accounts created.

To give you an idea of how unlikely that is, if every person on earth spent all their time doing nothing but generating Ethereum accounts, and they generated one a second, they'd only generate about 2^57 of them. To generate 2^80 and reach a 50% probability of finding a collision, they'd need to keep on generating one per second for about 8 million years.

-- https://ethereum.stackexchange.com/a/4300/105363