Skip to content
TrenchyBot

Transfers

This block sits inside Deployer Stats. It follows tokens sent out to other wallets.

Example transfers: percentage sent to wallets, tokens still held, recipient sales, total PnL, and a detail link.
Example · source-derived preview · Tap to enlarge
FieldMeaning / options
🔎 Transfers 0% ✅No direct recipient wallets were found in the available investigation.
⚠️ % to N walletsSupply transferred out and the number of direct recipients. + marks a minimum from partial history.
Found % still heldSupply located in the traced recipient wallets. ✅ zero; ⚠️ a positive balance; N/A unavailable.
LockedVerified Streamflow-locked tokens may appear, with release information when available. Locked tokens are still held, not burned.
Total bought / Total soldActivity across the traced recipients, in the displayed quote assets.
Total PnLEstimated result across the traced recipient wallets. This is separate from the deployer’s own wallet PnL.
view all transfer dataOpens the recipient-by-recipient trace.

Loading transaction history… / Loading transfer history… means the investigation is still running. A missing value does not mean zero.

Tap view all transfer data below the Transfers block. You can also use View Detailed Report → Deployer Transfers. All Transfers lets you choose other investigated wallets.

The address at the top is the source wallet for this trace. Its ATA link opens the token account used for this token.

Actual Telegram trace: 6.39% sent to 100 direct wallets; limits reached; 0.807% held across 50 traced wallets; partial buys and total sales.
Telegram screenshot · TIMELESS example · Tap to enlarge

In this example:

On screenHow to read it
Sent 6.39% to 100 direct walletsThe source sent 6.39% of the token supply to 100 direct recipients. This is transfer activity, not its current holdings.
Trace limits were hit; totals are partialThe investigation reached its wallet or depth limit. It has not followed every recipient or onward transfer.
Found 0.807% held across 50 traced walletsThose 50 checked wallets currently hold 0.807% of supply in total. The other recipients are not being counted as holding zero.
Total bought: 7.98 SOL (partial)Known buying across the traced recipients. The full total may be higher.
Total sold: 20.07 SOLDetected sales across the traced recipients. The overall trace is still partial, even if an individual line has no suffix.

100 direct recipients, 50 traced wallets, and five rows on the page describe different things: who received tokens, who was investigated, and what you are currently viewing.

Source → L1 → L2 → L3

  • L1: received tokens directly from the source wallet.
  • L2: received tokens from an L1 wallet.
  • L3: received tokens from an L2 wallet.

The from link identifies the sender for each step. Indented rows follow onward transfers. A Trace L… button opens that branch when more detail is available.

Telegram recipient row: L1 wallet received 0.12%, holds 0.14%, and shows SOL balance, buys, sales, and PnL.
Telegram screenshot · TIMELESS example · Tap to enlarge

In the first row, GGT6…rU9g received 0.12% but Holds 0.14%. That can happen because the wallet also bought tokens. Received supply and current holdings are different measurements.

RowMeaning
L1 [address] received %The recipient and the supply transferred to it along this path. The address link opens its token account.
from [address]The wallet that sent those tokens.
Holds % / $Current share of token supply and estimated USD value.
SOL / $The wallet’s SOL balance and its USD value—not the value of its token holdings.
Bought / SoldPurchases and sales found in that wallet’s investigated history, in SOL or another displayed quote asset.
PnLEstimated result including remaining holdings. It is not simply Sold − Bought: received tokens and liquidity activity can also affect the calculation.
Sent % to N walletsTokens sent onward. Child rows show the next layer of the trace.
LP Added / LP Removed / BurnedDetected liquidity changes or destroyed supply. These appear when present.
Locked / release detailsVerified Streamflow lock information, when present. Locked tokens still count as held.

Received % is a share of token supply, not a share of the sender’s wallet. Do not add every layer’s received percentage—the same tokens may move through several wallets.

Returned to source counts tokens sent back to the original wallet. It is cumulative transfer flow. Later holdings or sales at the source belong to that source wallet, rather than being counted again in the recipient totals.

Trace PnL summarizes the traced recipients. Partial Trace PnL covers the known portion only. PnL can be omitted when history, balances, or quote values do not support it.

Other messages explain gaps:

  • Loading / Investigating…: the trace is still running.
  • Refreshing trace history: shown totals come from the last completed trace.
  • History incomplete / limit exceeded / temporarily unavailable: some activity could not be included.
  • N/A: a balance is unavailable. + marks a known minimum.
Telegram page 1 of 10, rows 1–5 of 50 L1 wallets, next-page arrow, Back to All Transfer Traces, and trash button.
Telegram screenshot · TIMELESS example · Tap to enlarge

Page 1/10 · 1–5 of 50 L1 wallets means you are viewing five of the 50 traced L1 rows. The summary totals cover the trace, not just the five visible rows. Page size can shrink when rows contain long onward-transfer branches.

ControlAction
◀️ / ▶️Previous or next page. A dot means there is no page in that direction.
Trace L…Follow a recipient’s onward transfers.
Back to Transfer PageReturn from a branch to the previous trace page.
Back to All Transfer TracesReturn to the list of investigated source wallets.
🗑Close the message.

Next: Launchpad/DexLP Stats →