I can’t complete the requested on-chain trace from this state: the execution host is disabled, so I can’t run the required read-only chain calls. The evidence already gathered confirms 13.96M MARSCOIN left the BSC wallet on Oct. 6 and reached an unlabeled Ethereum wallet, which later split ETH into two equal transfers; it does not establish the full theft total, the fate of the reported Cash Cat and BP, or the complete laundering route.

$CASHCAT$MarsCoinOct 7, 2026, 07:02 UTC

Ask your own

Case file

$CASHCATCash Cat, robinhood, 0x020b…18b4

$MarsCoinbsc, 0xfe18…7777

Answered Oct 7, 2026, 07:02 UTC

Research trace 16

Latest posts of @cashcat_token
Latest posts of @cashcatsHOLO
Latest posts of @bnbMarsCoin
The page arkm.com
The supplied posts identify two reported wallet addresses but do not establish their chain attribution or transaction trail. Check attribution and search for independent on-chain references that can identify the incident’s timing and movement route.
The reports place the suspected theft around Oct. 6, but the BSC wallet’s outgoing transfers still need a bounded block range before its token movements can be traced. I’ll locate the incident-time BSC block and inspect the reported Solana wallet’s recent activity and attribution in parallel.
The supplied reports place the suspected theft on Oct. 6, and the BSC address is tagged as a MARSCOIN whale. I’m checking its token transfers during that day and retrieving the linked incident post for the claimed laundering route.
The BSC trace shows MARSCOIN moving into an intermediate wallet, while the incident report names ETH, BNB, SOL, Privacy Cash and Chainflip as routes. Identify the recipient wallets and find the original report before tracing their onward transfers.
The BSC logs show 13.96 million MARSCOIN leaving the reported wallet for an intermediate address, while the reported theft summary says the assets were converted and bridged onward. Pin down the swap transaction details and locate the Ethereum block window for tracing the intermediate wallet’s subsequent transfers.
The BSC transfers show the MARSCOIN proceeds going to an Ethereum address and a second recipient still needing identification. Check those wallets’ labels, the Ethereum wallet’s theft-window transfers, and the earlier token transfer receipt for conversion details.
The MARSCOIN proceeds reached an Ethereum address and were split into two transfers of the same token. Identify the recipients and inspect the source wallet’s other outgoing transfers to establish whether funds continued through a bridge or privacy service.
The prior logs show stolen MARSCOIN proceeds reaching two Ethereum wallets, then ETH leaving one of them in two equal transfers. Identify both recipients and retrieve the reported route details before following those wallets’ transfers.
The Ethereum recipient appears to have split ETH into two equal transfers, while the incident report attributes laundering to Privacy Cash and Chainflip. First identify those ETH recipients, then follow the BSC attacker’s BP sale and Cash Cat transfers to find additional proceeds and route addresses.
The BSC trace has confirmed MARSCOIN leaving the reported wallet, but the route for the other BSC assets and the ETH split recipients remains unresolved. Reconfirm recipient labels and locate the relevant BSC block window, while checking whether recent wallet history exposes the remaining transfers.
The latest history for the BSC-reported wallet shows two Robinhood-chain executions involving a suspected sender, but it does not establish the sender’s identity or account for the reported Cash Cat and BP losses. Identify that sender and locate the Robinhood-chain block window for the reported incident so its transfers can be traced.
The reported wallet history shows suspicious Robinhood-chain transactions involving the wallet and a token contract, but does not identify the drained assets or the next recipient. Trace the wallet’s incident-window transfers and label the counterparties first.