BitqueryBitqueryData Store
Solana logoSolanaTransfers

Solana Stablecoin Transfers

USDC and USDT transfers on Solana with DEX swaps removed: one row per payment, deposit or withdrawal, with sender, receiver, amount and USD value.

Coverage
Oct 30, 2025→ Nov 15, 2026 · yesterday
Rows
≈1.4Brows · estimate
Size
≈180 GBParquet · estimate
Table
1stablecoin_transfers
Columns
47typed
Coverage ends yesterday, UTC

Overview

Solana stablecoin transfers are every USDC and USDT transfer on Solana that is not part of a DEX swap. Most stablecoin movement on Solana is trading: on 7 November 2026 there were 16.1 million USDC and USDT transfer rows, and 76% of them sat in transactions that also hold a decoded DEX trade. We drop every transfer in such a transaction, so what is left is payments, exchange deposits and withdrawals, treasury moves and other transfers, about 3.9 million rows a day. Rows keep the standard Solana transfers schema, 47 columns, the same as our other Solana transfer sets.

Most buyers start with wallets: group Transfer_Amount by Transfer_Sender_Token_Owner and Transfer_Receiver_Token_Owner, which are the wallets, not the token accounts. Keep Transaction_Result_Success = 'true' for settled payments, and decide what to do with dust: about 15% of sample rows move less than one cent, the pattern of address-poisoning spam.

Use cases

  • Stablecoin payment volume and counts on Solana, without swap noise
  • Exchange, merchant and payroll flows for known wallets
  • USDC and USDT balance changes per wallet over time
  • Screening counterparties of a wallet's stablecoin payments

Table

47 columns · free sample for the table

stablecoin_transfers

47 columns

One row per USDC or USDT transfer on Solana outside DEX swap transactions. Standard Solana transfers schema, 47 columns.

solana/solana-stablecoin-transfers/stablecoin_transfers<YYYY-MM-DD>.parquetone file per UTC day, sorted by slot
Browse columns Sample fileSample updated Nov 16, 2026

Schema reference

copies a column name
47 columns
ColumnTypeDescription
Block4
Block_DateDateUTC date of the block
Block_HeightUInt64Count of blocks produced before this one; lower than the slot because some slots are skipped
Block_SlotUInt64Slot number of the block; delivered files are split by slot range
Block_TimeDateTimeBlock timestamp, UTC
Instruction7
Instruction_CallPathArrayInstruction_Index values of the parent instructions; empty on a top-level instruction
Instruction_ExternalSeqNumberUInt32Number of the top-level instruction this row falls under, counting from 1
Instruction_IndexUInt32Position of the instruction in the transaction, counting inner instructions
Instruction_InternalSeqNumberUInt32Position under its top-level instruction, counting from 1; 0 on a top-level instruction
Instruction_Program_AddressStringProgram that executed the instruction
Instruction_Program_MethodStringDecoded instruction name, for example swap, buy or route
Instruction_Program_NameStringDecoded program name
Transaction8
Transaction_FeeStringNetwork fee paid, in SOL
Transaction_FeeInUSDFloat64Network fee, in USD
Transaction_FeePayerStringWallet that paid the network fee; Solana makes it the first signer
Transaction_IndexUInt32Position of the transaction within the block
Transaction_Result_ErrorMessageStringError the runtime returned when the transaction failed; empty on success
Transaction_Result_SuccessStringWhether the transaction succeeded
Transaction_SignatureStringTransaction signature, base58
Transaction_SignerStringWallet that signed the transaction and paid its fee
Transfer8
Transfer_AmountStringAmount transferred, decimal adjusted, as a decimal string. Multiply by 10^Transfer_Currency_Decimals for the raw on-chain integer
Transfer_AmountInUSDFloat64Amount valued in USD at the hourly price for the block's hour; 0 for tokens with no price
Transfer_Authority_AddressStringAccount that authorised the transfer, usually the token account owner or its delegate
Transfer_IndexUInt32Position of the transfer within the transaction
Transfer_Receiver_AddressStringReceiving token account, base58; for SOL the receiving wallet
Transfer_Receiver_Token_OwnerStringWallet that owns the receiving token account; the address you usually want
Transfer_Sender_AddressStringSending token account, base58; for SOL the sending wallet
Transfer_Sender_Token_OwnerStringWallet that owns the sending token account; the address you usually want
Transfer_Currency20
Transfer_Currency_CollectionAddressStringNFT collection of the transferred token; empty for fungible tokens
Transfer_Currency_DecimalsUInt32Decimals of the transferred token
Transfer_Currency_EditionNonceUInt32Metaplex edition bump seed of the transferred token; a technical value, 0 when unset
Transfer_Currency_FungibleStringWhether the transferred token is fungible; the string true or false
Transfer_Currency_IsMutableStringWhether the transferred token's metadata can still be changed; the string true or false
Transfer_Currency_KeyStringMetaplex metadata account type of the transferred token, such as MetadataV1
Transfer_Currency_MetadataAddressStringMetaplex metadata account of the transferred token, when recorded
Transfer_Currency_MintAddressStringMint address of the transferred token and the key for joins; SOL shows as 11111111111111111111111111111111 (native) or So11111111111111111111111111111111111111112 (wrapped)
Transfer_Currency_NameStringName of the transferred token
Transfer_Currency_NativeStringtrue for SOL, false for every SPL token; the string true or false
Transfer_Currency_PrimarySaleHappenedStringWhether the transferred token's first sale has happened, from Metaplex metadata; the string true or false
Transfer_Currency_ProgramAddressStringProgram that owns the transferred token's mint, SPL Token or Token-2022, when recorded
Transfer_Currency_SellerFeeBasisPointsUInt32Creator royalty on the transferred token in basis points (100 = 1%); 0 for nearly all fungible coins
Transfer_Currency_SymbolStringSymbol of the transferred token; reported by the token metadata, not unique
Transfer_Currency_TokenCreator_AddressArrayCreator wallets from the transferred token's metadata; mostly empty in this table
Transfer_Currency_TokenStandardStringMetaplex standard of the transferred token, such as Fungible or FungibleAsset, when recorded
Transfer_Currency_UpdateAuthorityStringAccount that can change the transferred token's metadata unless it is immutable; NativeLoader1111111111111111111111111111111 for SOL
Transfer_Currency_UriStringLink to the transferred token's off-chain metadata file, often on IPFS or Arweave
Transfer_Currency_VerifiedCollectionStringWhether the transferred token's NFT collection is verified; false for fungible tokens
Transfer_Currency_WrappedStringWhether the transferred token is wrapped SOL; the string true or false
Sample file

Ask an AI about this data

Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief first, so the answer comes from the real column list rather than a guess.

Start with

Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.

Delivery

Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:

# stablecoin_transfers: one file per UTC day, sorted by slot
solana/solana-stablecoin-transfers/stablecoin_transfers<YYYY-MM-DD>.parquet
  1. Download a free sampleNo email needed.
  2. Pay nowName, work email and licence check.
  3. Pay the invoiceBy card or bank transfer.
  4. Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.

Need new data after your purchase?

Kafka Streams sends new Solana data in real time, so your copy can stay current after the files end. It is sold on an Enterprise plan.

Read the Kafka docs

Time windows

Every window includes 47 columns. Only the time range changes.

31 days
Latest month
Oct 15, 2026 → Nov 15, 2026
$150
Pay now
184 days
Last 6 months
May 15, 2026 → Nov 15, 2026
$600
Pay now
365 days
Last 12 months
Nov 15, 2025 → Nov 15, 2026
$1,000
Pay now
In every window
  • The stablecoin_transfers table, 47 columns
  • Parquet files in the layout under Delivery
  • S3 or R2 download, chosen at checkout
  • Licensed under the Data License

FAQ

10 questions
What is in the Solana Stablecoin Transfers dataset?

One Parquet table, stablecoin_transfers, with 47 columns: every transfer of USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v) or USDT (Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB) on Solana in the window you buy, except transfers inside DEX swaps. Each row has the sending and receiving token accounts and wallets, the amount, a USD value, the fee and the transaction it settled in.

How are swaps excluded?

A transfer is dropped when its transaction contains at least one decoded DEX trade on the same day, on any DEX and any pair, failed trades included. That removes the stablecoin side of swaps and the routing hops of aggregator trades. In three 18-minute slices of 7 November 2026 it removed 515,901 of 674,855 stablecoin transfer rows, 76.4%.

How big is it?

About 3.9 million rows a day, so roughly 117 million a month and 1.4 billion for 12 months. That is estimated from full-day stablecoin counts on three days (14.3 to 19.1 million rows) times the 23.6% kept after swap removal. At about 129 bytes per row as ZSTD Parquet, measured on 1,991 rows from that day, 12 months is around 180 GB. All figures are approximate until the delivery manifest.

How do I measure payment volume for one wallet?

Filter Transfer_Receiver_Token_Owner or Transfer_Sender_Token_Owner to the wallet and Transaction_Result_Success to 'true', then sum Transfer_Amount in and out per day. Use the Token_Owner columns, not Transfer_Receiver_Address and Transfer_Sender_Address, which are token accounts that a wallet can have several of.

What was left out, and why?

Transfers in swap transactions, other stablecoins (PYUSD, USDS, bridged USDT variants) and native SOL. Mints and burns are not transfers, so new USDC issued by Circle appears only when it is first sent on. Failed transactions stay in, about 2.5% of rows in the test slice, marked by Transaction_Result_Success.

How were the rows produced and checked?

From our Solana archive of transfer and DEX trade instructions. The export was run on a slice of 7 November 2026 (slots 466,662,738 to 466,667,737): 282,070 stablecoin transfer rows, 219,323 in swap transactions, 62,747 kept, worth $74.1 million, all 47 columns typed as the published Solana transfers files. The free sample is 100 rows from slot 466,502,738 onward, 11:54 UTC the same day.

What should I watch out for?

Transfers made by programs we do not decode as DEXes stay in, for example some arbitrage bots, lending and bridge programs; Instruction_CallPath shows whether a transfer was top-level (empty) or called by another program, which was the case for 69% of sample rows. About 15% of sample rows move less than $0.01, mostly address-poisoning dust. Instruction_Program_Name reads spl_token_2022 for both token programs, so use Instruction_Program_Address to tell them apart.

How is the USD value set?

Transfer_AmountInUSD is the amount times our price for the token at the block time, so it sits close to the token amount, for example $953.28 for 954.457567 USDT. Use Transfer_Amount if you want both coins counted at exactly one dollar.

How do I load it?

One line in DuckDB: SELECT * FROM read_parquet('stablecoin_transfers/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path). The sample file opens without credentials.

How current is it, and how is it delivered?

Complete days start on 30 October 2025, and our Solana archive runs about 8 days behind, so a purchase covers up to about 8 days before delivery. Files are Parquet, ZSTD-compressed, one per UTC day and sorted by slot, with a JSON manifest listing each file and its sha256. We prepare them within 7 business days of purchase and email you the location: a Requester Pays S3 bucket downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only key, as chosen at checkout. Files stay available for 7 days from delivery.