Ethereum Foundation-linked wallets and the reported 4,393 ETH Kraken transfer: the supplied reports say two historically linked wallets sent 4,393 ETH, about $11.13 million, to Kraken, but the on-chain records available here do not confirm that transfer or establish a sale. EmberCN reports that the wallets received 59,751 ETH from an Ethereum Foundation wallet about ten years ago and that 49,751 ETH was sent to Kraken over time at an average price near $658 (EmberCN).

$ETHOct 12, 2026, 06:24 UTC

What the wallet records show

Arkham links 0x06f0…8483 to Ethereum’s first funder, 0x999D…229c and 0x4c4F…2b94 to the first wallet, and identifies the first wallet’s counterparty as the Ethereum Foundation. The two latter wallets’ historical counterparties include Kraken deposit addresses. At the latest reported balance read, the second wallet held about 5,000.37 ETH, roughly $12.78 million, while the first funder wallet showed no ETH balance.

Recent transfer evidence

The cited transaction 0x0175…2a84 has zero native ETH value and contains numerous token logs, including transfers involving contracts indexed as ETH lookalikes and flagged as suspicious. The recent transfer rows for the two supplied wallets likewise show lookalike token contracts rather than a verified 4,393 ETH movement. A transfer to an exchange, even if confirmed, would show a deposit, not prove that a sale took place.

The sources do not name a verified transaction hash for the claimed 4,393 ETH deposit or establish whether the deposited ETH was sold. Lookonchain’s report and EmberCN’s post give the claim and historical totals.

Ask your own

Case file

$ETHEthereum, ethereum

Answered Oct 12, 2026, 06:24 UTC

Sources 6

EmberCNx.com
0x06f0…8483etherscan.io
0x999D…229cetherscan.io
0x4c4F…2b94etherscan.io
0x0175…2a84etherscan.io
Lookonchain’s reportx.com

Research trace 9

The page arkm.com
The page t.me
The previous reads provided the claimed wallets and deposit amount but did not expose chain data. Retrieve each wallet’s transfer history, current balance, exchange/entity label, and EmberCN’s post in parallel; transfer results will supply hashes for direct transaction verification.
Verify the cited recent transaction and on-chain ETH movement, plus check the third supplied wallet and how the second wallet’s counterparties are labeled. The indexed recent transfer rows include suspicious token contracts and do not themselves establish a Kraken ETH deposit.
The cited recent transaction and block logs did not identify either supplied wallet in canonical ETH transfers; indexed rows instead include lookalike or suspicious token contracts. These reads extend both wallets’ transfer records and independently check their Kraken counterparties and transaction histories for the reported sale and the claimed cumulative history.
The cited 4,393 ETH still has not been verified in canonical token transfers; earlier recent rows include suspicious tokens and show substantial current ETH balances. These reads check canonical ETH outflows from both linked wallets and trace Kraken-labelled recipients while seeking confirmation of the historical total.
The previous results expose suspicious lookalike token rows instead of canonical ETH, plus Kraken-labelled addresses in the wallets’ counterparty histories. These reads check native ETH transfers, the reported transaction hash, and both linked wallets’ full indexed histories.
The claimed 4,393 ETH is still unverified on-chain: recent indexed rows for the two linked wallets include suspicious lookalike tokens, while Kraken-labelled counterparties show older exchange flows. This remaining history page may clarify what the third supplied wallet did over time.
The prior steps left no available reads that can resolve the reported 4,393 ETH transfer: wallet history shows recent lookalike token transfers, and the alleged native ETH deposit is not confirmed by the cited transaction or the indexed wallet records. The remaining supported findings answer what the linked histories show and the limits of calling a Kraken deposit a sale.