FLOWS BETWEEN TWO ADDRESS SETS on Arc (arc, ARC, Arc Network, Circle Arc): every successful transfer (tokens and native
USDC) from any address of set A to any address of set B, and back, in ONE call - "did these
wallets ever pay those wallets", "how much moved between my suspects and the exchange
wallets", "which of these deposit addresses sent to that hot wallet". Pass up to
50 addresses per set separated by "|" (0xabc…|0xdef…). A longer list is not an error:
the first 50 distinct addresses of each set are used and the rest are ignored -
every row reports A_Addresses_Requested / A_Addresses_Used and B_Addresses_Requested /
B_Addresses_Used, so compare them and split a longer set into several calls. Leave addresses_b EMPTY to get every
counterparty of the A set, both directions, grouped per A address - the multi-address form of
arc_flow_edges.
mode="summary" (default) returns one row per (Direction, Sender, Receiver, token) with
Transfers, total Amount, First_Time, Last_Time and the latest Tx, ordered by `sort`.
mode="rows" returns the individual transfers newest first; page with cursor: pass the Cursor
value of the LAST row, with all other arguments unchanged, to get the next page (a summary row
carries no Cursor). A rows-mode row is a LEDGER LINE: besides the amount it carries Amount_Raw (the
exact integer amount in the token's smallest unit) with Decimals, Block and Tx_Index, and Price_Usd
(the token's USD price at the time of the transfer), Value_Usd = Amount x Price_Usd and
Price_Status - "ok"; "no_price" = no price is known for this token at that time, so Price_Usd and
Value_Usd are empty (never read that as zero); "suspect" = the stored price is more than twice the price one day earlier AND one day later, or
less than half of both - a likely data glitch - so Value_Usd is left empty - check it with
price_at. A token has ONE price per day, so its value is approximate. USDC on Arc - the native coin and the ERC-20 at 0x3600000000000000000000000000000000000000 - always reads no_price here: it is USDC, so price it as USDC on Ethereum with price_at. On a summary row those seven columns are empty: a total over a
period has no single price. Self = 1 (both modes) marks a movement whose counterparty is another
address of set A - a move inside the set, not income and not spending.
Direction A_TO_B = sent by an A address to a B address, B_TO_A = sent by a B
address to an A address; an address listed in both sets appears in both directions. With
addresses_b empty the same holds for a transfer between two A addresses: it is listed as A_TO_B
for its sender AND as B_TO_A for its receiver, so never add rows of both directions together.
WINDOW: the last `days` days (default 30, at most 366) ending at before_time, or now;
after_time sets the start instead, within the same 366-day limit. Window_From / Window_To
on every row show the range searched; for an older period set before_time. An empty result means
no transfer between the sets in that window.
COST: the search is keyed on set A, so put the SMALLER and less busy set in addresses_a -
individual wallets, not exchange hot wallets, bridges or token contracts. If the call fails
with a row-limit error ("Limit for rows ... exceeded"), swap the two sets, shorten days, or
split set A. Cost also grows with the number of addresses in set A times the window.
Each row carries the token Contract (empty for native USDC); a symbol alone can match
look-alike clones, so pin one token with contract, or restrict to native or tokens with
asset_type. Amount is in TOKEN UNITS: totals of different tokens must not be compared or added
together, there is no usd filter (min_amount is in token units), and sort="amount" is only
meaningful with one token pinned. To identify the addresses, pass them to
labels_for_addresses.
USDC ON ARC IS ONE ASSET WITH TWO INTERFACES that share a single balance: the NATIVE coin that pays
for gas (Native = 1, no contract, 18 decimals) and the ERC-20 token at
0x3600000000000000000000000000000000000000 (6 decimals). Each movement is listed once, under the
interface that carried it, so the two together are the address's USDC flow - asset_type="usdc"
selects both at once. Over a thousand OTHER contracts on this chain also print the symbol USDC and
they are unrelated tokens: never identify an asset by its symbol, use Contract and Native.
On Arc most USDC moves through contract code, so internal transfers are counted by default; pass include_internal=0 for top-level transfers only.
