Blockchain records do not prove my entire complaint — but they do not forget a transfer.
The hashes below can be checked independently on BscScan. They show on-chain activity and token movement. They do not, by themselves, prove what LioGames credited internally or what business label applied to each payment — but they prove the money moved, which is what LioGames denies.
Two July 24 transfers at the center of my complaint
Disputed transfer 01
From my LBank-side withdrawal record
0xf56f5480615b841af9f06c46fa9567f0e4d62df90372dff3d5ab92081853d04f4,119 USDT
Disputed transfer 02
From my CoinEx-side withdrawal record
0x0ebfeea4bfb7d8e0eb931705395698083223c3793976f0b56b0611e0e36c3646800.57 USDT
Total shown in my complaint: 4,919.57 USDT.
Earlier transactions are included because this was not a first-time account
I had funded/used the account before the July dispute. These earlier hashes are historical context for why I trusted the platform enough to send a much larger amount later.
Earlier transfer 03
0x21db57ef412bc72c2f4285af8c6e096f59326e46fb8d23a6774c5e76695b4cffEarlier transfer 04
0xbe7319d4f1ae644b403fad4fd94f5e7e474a284856ea54bd149d6bd586e98d79What a TXID proves and what it does not
| Question | Can a public BSC transaction answer it? |
|---|---|
| Did this on-chain transaction occur? | Yes, if confirmed on BscScan. |
| What token amount moved? | Generally yes, from the token-transfer logs. |
| Was the payment intended for VIP/H2H? | No. Business purpose needs invoice/account context. |
| Was the receiving address controlled by LioGames? | Only if separately tied to LioGames through reliable records. |
| Was my internal account credited, locked or modified? | No. That is off-chain platform information. |
That is why I publish the TXIDs alongside screenshots, screen recordings and the company response instead of pretending one type of evidence proves everything.