Every SOL transfer a Pump.fun creator wallet received in the 24 hours before launching, in the standard Solana transfers schema, to trace who funded each launch.
Fresh creator wallets are usually funded minutes before a launch. This dataset keeps every SOL transfer each Pump.fun creator wallet received in the 24 hours before its first launch of the day, so the sender column names the funder.
Rows are the standard Solana transfers schema, 47 columns, with nothing renamed or added. Join to the Pump.fun Token Registry on creator to tie each funding transfer to the tokens it paid for.
Use cases
Funder and dev-wallet clustering
Serial launchers behind fresh wallets
Risk screening of new launches
Table
47 columns · free sample for the table
pumpfun_creator_funding
47 columns
SOL received by each creator wallet in the 24 hours before its launch, in the standard Solana transfers schema.
solana/pumpfun_launch/creator_funding<YYYY-MM-DD>.parquetone file per creation day
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
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.
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:
# pumpfun_creator_funding: one file per creation day
solana/pumpfun_launch/creator_funding<YYYY-MM-DD>.parquet
Download a free sampleNo email needed.
Pay nowName, work email and licence check.
Pay the invoiceBy card or bank transfer.
Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.
Time windows
Every window includes 47 columns. Only the time range changes.
Tokens created from 28 October 2025, the first day with complete raw Solana trades in our archive. A 12-month purchase starts there until the rolling window passes that date. Earlier Pump.fun history exists only as aggregated candles and volume, which these tables do not use.
How current is it?
Our Solana pool and transfer archive runs about 8 days behind, so a purchase covers up to about 8 days before delivery.
What counts as funding?
Native SOL transfers into the creator wallet in the 24 hours before that creator's first launch of the day. SPL token transfers are not included.
How do I load it?
With DuckDB: SELECT * FROM read_parquet('pumpfun_creator_funding/*.parquet') LIMIT 10. pandas, Polars, Spark and ClickHouse read the same files.
Can I try before I buy?
Yes. The table links to a public sample file from 1 October 2026: creators who launched in slots 452,148,504 to 452,149,503 (02:07 to 02:14 UTC). The sample looks back about 2 hours, not the full 24. No email address required.
How is the data delivered?
As flat Parquet files (ZSTD) under a stable layout, one prefix per table, with a JSON manifest listing each file and its sha256. We prepare the files within 7 business days of purchase and email you the location. You choose at checkout where to collect them: a Requester Pays S3 bucket, downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only API key and no egress fees. Files stay available for 7 days from delivery.