/v4/data/staking/native/transactions

100 credits per API call

Get staking-related transactions for a Solana stake account or Ethereum withdrawal address. Returns deposits, topups, withdrawals, and credential changes.

Response shape differs by chain: Solana returns stakeAddress and transactions with stakeAddress/validatorAddress; Ethereum returns withdrawalAddress and transactions with withdrawalAddress/validatorIndex/validatorPubkey.

Supported blockchains:

• Solana - solana-mainnet (create, stake, unstake, withdraw, split)
• Ethereum - ethereum-mainnet (create=deposit, stake=topup, withdraw=withdrawal, credential_change=BLS→execution change)

Ethereum-specific: For beacon-only events (withdrawals, credential_change), txHash is a synthetic reference ID, not an on-chain execution transaction hash. blockNumber for credential_change is the consensus slot. amount is in ETH. Results are limited to 100,000 transactions per request; use type, timeFrom/timeTo, or epochFrom/epochTo filters for addresses with more history.

To get started:

• Provide a chain and stake address (Solana stake account or Ethereum withdrawal address). The API will return all staking-related transactions.
• You can filter transactions by type using the type parameter. Chain-specific: Solana supports create, stake, unstake, withdraw, split (not credential_change); Ethereum supports create, stake, withdraw, credential_change (not unstake, split). Using an unsupported type for a chain returns 400.
• You can filter transactions by epoch range using epochFrom and epochTo parameters.
• You can filter transactions by block range using blockFrom and blockTo parameters.
• You can filter transactions by time range using timeFrom and timeTo parameters (ISO 8601 format).
• You can filter transactions by unix timestamp range using unixFrom and unixTo parameters.
• Important: You can only use one filter type at a time. Valid combinations: (epochFrom/epochTo), (blockFrom/blockTo), (timeFrom/timeTo), (unixFrom/unixTo). You cannot mix different types like epochFrom with blockTo.
• Transactions are sorted by epoch in descending order (newest first).