Lookonchain reports that U.S. government wallets transferred 834 BTC, valued at $71.56 million, and 40,285 BNB, valued at $31.63 million, on Oct. 7. It says the BTC was deposited into Coinbase Prime (Lookonchain).

$BTC$BNBOct 7, 2026, 01:51 UTC

Cointelegraph describes the activity as more than $103 million moved over nine hours, reporting 833 BTC and 40,285 BNB sent to unlabeled addresses (Cointelegraph). OnchainLens gives a more precise BTC amount of 833.599 BTC and names a fresh BNB recipient, 0x6fB3…5A579, attributing the BTC to Potapenko/Turogin and Bitfinex forfeitures and the BNB to FTX/Alameda seized funds (OnchainLens).

These are reports of transfers; the available evidence here does not independently establish the transaction details or that the Coinbase Prime deposit resulted in a sale.

Ask your own

Case file

$BTCBitcoin, bitcoin

$BNBbsc

Answered Oct 7, 2026, 01:51 UTC

Sources 4

Research trace 13

The page arkm.com
The supplied posts say Arkham attributed transfers of 834 BTC and 40,285 BNB to U.S. government wallets, with the BTC sent to Coinbase Prime. Verify the original posts and identify the government wallets and transfer transactions so the amounts and destination can be checked on-chain.
The supplied page is an entity page rather than a wallet address, so its ownership lookup could not identify the underlying wallets. Search for Arkham’s contemporaneous report and the named exchange deposit address to locate concrete on-chain transaction identifiers and verify the BTC and BNB legs.
The posts establish the amounts and destination as reported, but the entity-page link did not identify wallet addresses. Search for later or independent reports that name the transactions or addresses before attempting on-chain verification.
The reports identify transfer amounts but not the wallets or transaction hashes needed to verify them. The prior search surfaced a secondary post naming a BNB address prefix and a more precise BTC amount; first resolve those leads to exact addresses before reading transfers.
The posts and follow-up chatter still do not give complete wallet addresses or transaction hashes, so the transfer claims cannot yet be checked on-chain. I’ll try alternate search terms for the precise BTC amount, the BNB address fragment, and reported government-wallet movements.
The prior search surfaced an exact BNB recipient address in a secondary post. Resolve its label first, then check whether the BNB transfer and any later movement can be identified from its on-chain token logs.
The lead identifies a fresh, unlabeled BSC recipient. I need the reported-time block range and its BNB transfers to test whether this address received the reported 40,285 BNB and identify the sender.
The BNB recipient candidate is unlabeled, and the previous log query did not cover the reported transfer time. Find the report’s precise timing and bracket it with a BSC block so the next step can query BNB transfers to that recipient.
The supplied reports say the BNB moved through multiple wallets, and the prior step placed the report around 18:00 UTC on Oct. 6. Check BNB token transfers into the named fresh recipient and label any sender before tracing further.
The BNB recipient has already been identified as an unlabeled BSC address, but the prior log request fell outside the supported block window. Check its owner and query BNB transfers to it in a narrower range around the reported movement.
The BNB recipient candidate is a full address, but earlier log queries used an invalid token contract filter and an overly broad range. Resolve the native BNB representation on BSC and check a focused transfer window around the reported movement.
The supplied posts and follow-up reports agree on the transfers, but no exact transaction evidence was recovered. Summarize what the posts report while distinguishing that reporting from independently verified wallet activity.