← Back to research

Where Did This Wallet Send Its Funds? Tracing Outflows on EVM and Robinhood Chain

Trace where an EVM or Robinhood Chain wallet sent its tokens, using a real transfer readout, wallet age checks and the caveats to verify on an explorer.

By Stalkchain ResearchPublished Oct 8, 2026Updated Oct 8, 20267 min read
Wallet TransfersRobinhood ChainEVM

Quick answer

Call stalkchain_wallet_transfers with an EVM address and a chain to list its token and native transfers, newest first, each marked in or out. On Oct 8, 2026, one Robinhood Chain wallet sent three different tokens to a single address in under a minute. Symbols only come back, so confirm the tokens on an explorer.

This guide is about outflows. Where money came from is a different question, and the Solana funding-source guide covers it. Here the question is where a wallet sent assets, on EVM chains including Robinhood Chain (4663), where wallet_transfers works. It does not work on Solana addresses.

How do you see where a wallet sent its tokens?

List its transfers and filter to the ones marked out. Then group them by receiving address. Three sends to one address tell you more than three sends to three addresses.

Plain-English prompt for Claude or ChatGPT with the StalkChain connector:

Show the last five transfers for 0x0ecb…2b on Robinhood Chain and tell me where the outgoing ones went.

The call:

stalkchain_wallet_transfers
{ "wallet": "0x0ecb3d3be6cec00242798aa56f8df26477fd4c2b", "chain": "robinhood", "limit": 5 }

The response:

{
  "wallet": "0x0ecb…2b",
  "chain": "robinhood",
  "count": 5,
  "transfers": [
    { "at": "2026-10-07T06:51:26.000Z", "asset": "FDOG", "amount": 1, "direction": "in", "from": "0xdf20...bebb6" },
    { "at": "2026-10-07T00:15:06.000Z", "asset": "STARSHIP", "amount": 5000, "direction": "out", "to": "0xb92f…ff4f" },
    { "at": "2026-10-07T00:14:58.000Z", "asset": "BONER", "amount": 321.87, "direction": "out", "to": "0xb92f…ff4f" },
    { "at": "2026-10-07T00:14:08.000Z", "asset": "PRIORS", "amount": 25086.61, "direction": "out", "to": "0xb92f…ff4f" },
    { "at": "2026-10-06T22:03:08.000Z", "asset": "SOLANA", "amount": 471.62, "direction": "in", "from": "0x0c52...938d" }
  ]
}

Pulled Oct 8, 2026, about 06:15 UTC via StalkChain's MCP (stalkchain_wallet_transfers). The wallet is the EVM address of the public FOMO handle GL_AW_AT_PARAGON. Counterparty addresses are shortened here.

Same call over REST:

curl -G https://data.stalkchain.com/api/v1/tools/stalkchain_wallet_transfers \
  -H "Authorization: Bearer sc_YOUR_API_KEY" \
  -d wallet=0x0ecb3d3be6cec00242798aa56f8df26477fd4c2b \
  -d chain=robinhood \
  -d limit=5

What does each field in the transfer payload mean?

  • at: the UTC time of the transfer. The list is newest first.
  • asset and amount: the token symbol and the amount in token units. There is no USD value, so you cannot rank sends by dollar size from this call alone.
  • direction: in or out relative to the wallet you queried.
  • from or to: the counterparty. For an out row, to is the receiver.

Three oddities worth knowing before you quote anything:

  1. Symbols, not contracts. The payload carries a ticker with no contract address. Clone tokens reuse tickers, so "STARSHIP" here could be more than one token. Match the transfer to the exact contract on an explorer before you name a token.
  2. Mixed address formatting. The first outgoing row returned the full receiver address, while others came back shortened with an ellipsis. Treat the shortened ones as display strings and confirm the full address from the explorer before pasting it into another query.
  3. Spam shows up. The 1 FDOG received at 06:51 on Oct 7 is the kind of dust airdrop that appears in many wallets. Incoming rows from unknown senders are not a signal.

What patterns count as meaningful outflows?

Read the three outgoing rows together:

Time (UTC, Oct 7)TokenAmountReceiver
00:14:08PRIORS25,086.610xb92f…ff4f
00:14:58BONER321.870xb92f…ff4f
00:15:06STARSHIP5,0000xb92f…ff4f

Three tokens, one receiver, 58 seconds from first to last. That is a sweep: someone moved several balances out of one wallet in a single sitting.

A sweep has more than one innocent explanation. The wallet owner may be consolidating into another wallet they control, moving to cold storage, paying a counterparty or depositing to a venue. It can also precede a sale from the receiving address. The transfer list cannot tell you which.

Patterns that deserve a closer look:

  • Many tokens to one address in minutes. A sweep, as above.
  • A large send right after a large receive. Pass-through behaviour.
  • Sends to an address that is brand new. See the next section.
  • The same receiver across several of the wallet's chains. Run the same query per chain.

How do you check who received the funds?

Check the receiver's age. stalkchain_wallet_age returns the first transaction date, age in days and the count of outbound transactions per EVM chain. A receiver that is hours old and has never sent anything looks very different from one with months of history.

First, the sender's own age profile:

stalkchain_wallet_age
{ "wallet": "0x0ecb3d3be6cec00242798aa56f8df26477fd4c2b" }
{
  "oldestAgeDays": 23,
  "activeChains": 3,
  "chains": [
    { "chain": "robinhood", "firstSeen": "2026-09-15T00:07:15.000Z", "ageDays": 23, "outboundTxCount": 5 },
    { "chain": "ethereum",  "firstSeen": "2026-09-29T00:26:47.000Z", "ageDays": 9,  "outboundTxCount": 1 },
    { "chain": "base",      "firstSeen": "2026-09-17T05:53:25.000Z", "ageDays": 21, "outboundTxCount": 1 },
    { "chain": "bsc",        "firstSeen": null, "outboundTxCount": 0, "active": false },
    { "chain": "monad",      "firstSeen": null, "active": false },
    { "chain": "hyperliquid","firstSeen": null, "active": false }
  ]
}

The sender is 23 days old on Robinhood Chain and active on three of six chains. Note the chain list: transfers above covered only Robinhood Chain, so Ethereum and Base outflows need their own calls.

Then the receiver, restricted to Robinhood Chain:

stalkchain_wallet_age
{ "wallet": "0xb92f…ff4f", "chains": ["robinhood"] }
{ "oldestAgeDays": 113, "activeChains": 1,
  "chains": [ { "chain": "robinhood", "firstSeen": "2026-06-17T14:05:27.000Z", "ageDays": 113, "outboundTxCount": 1, "active": true } ] }

Pulled Oct 8, 2026 via StalkChain's MCP (stalkchain_wallet_age).

The receiver is 113 days old, far older than the sender, and has sent exactly one transaction ever. That fits a long-held wallet that mostly receives, such as a personal vault or a deposit address.

It does not fit a throwaway made for this transfer. It still does not prove the two wallets share an owner.

How do you verify a wallet transfer on an explorer?

Use the transfer list as a lead, then confirm on a block explorer for the chain. For each outflow:

  1. Search the sender address and find the transaction at the at timestamp.
  2. Open the token contract in the transfer and compare it to the project's published contract. This fixes the clone-symbol problem.
  3. Copy the full receiver address from the explorer.
  4. Check the receiver's own history, including what it did next. If it sold the tokens within minutes, that changes the story.
  5. Record the transaction hash for anything you intend to cite.

The tool's payload in this pull did not show a transaction hash on the rows, so the timestamp and amount are your search keys.

How is this different from tracing a wallet's funding?

Direction and chain. The funding-source workflow asks who paid for a Solana wallet to exist. This one asks where an EVM wallet's assets went after it held them.

For Solana address history, start with reading a wallet's transaction history and checking whether a Solana wallet is still active. For the Robinhood Chain side of wallet research, see how to track wallets on Robinhood Chain.

Chain coverage is the practical limit. wallet_transfers and wallet_age are EVM only. The chains are Ethereum, Base, BNB Chain, Monad, HyperEVM and Robinhood Chain. Query each chain you care about, since one call covers one chain for transfers.

The data lives behind the StalkChain MCP server. Chain pages like Robinhood Chain data for AI agents and Ethereum data for AI agents list the related tools, and Ethereum data in Codex shows the setup in a coding agent. Pricing starts with a $5 free credit.

Data, not financial advice. A transfer is a movement, not a verdict.

FAQ

How do I trace where a wallet sent its tokens?

Call stalkchain_wallet_transfers with the EVM address and a chain, then keep the rows marked out. Group them by receiving address and time. Confirm each token and receiver on a block explorer, because the payload returns symbols rather than contract addresses.

Does wallet transfer history work for Solana wallets?

No. stalkchain_wallet_transfers and stalkchain_wallet_age are EVM only. They cover Ethereum, Base, BNB Chain, Monad, HyperEVM and Robinhood Chain. For Solana, use transaction-history tools and the funding-source workflow.

Does a transfer to another wallet mean the owner sold?

Not by itself. The owner may be consolidating, storing or paying someone. Check what the receiving wallet did next on an explorer. A quick sale from the receiver is a stronger sign than the transfer alone.

How do I tell if the receiving wallet is new?

Run stalkchain_wallet_age on the receiver. It returns the first transaction date, age in days and outbound transaction count per chain. In the example above the receiver was 113 days old with one outbound transaction.

Why does the same ticker appear for different tokens?

Transfers return the symbol only, and clone tokens reuse tickers. Open the transaction on an explorer and read the token contract before treating a symbol as a specific project.

Does the transfer list show dollar values?

Not in this readout. Rows carry amount in token units, so price the token separately if you need a USD figure.