Cross Chain
Balances
Transactions
- GETGet a transaction
- GETGet transaction summary for address
- GETGet earliest transactions for address (v3)
- GETGet recent transactions for address (v3)
- GETGet paginated transactions for address (v3)
- GETGet bulk time bucket transactions for address (v3)
- GETGet all transactions in a block by page (v3)
- GETGet all transactions in a block (v3)
NFT
- Core Rendering
- Market Data
- Ownership & Token Gating
Bitcoin
Get all transactions in a block (v3)
Commonly used to fetch all transactions including their decoded log events in a block and further flag interesting wallets or transactions.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The chain name eg: eth-mainnet.
The requested block hash.
The currency to convert. Supports USD, CAD, EUR, SGD, INR, JPY, VND, CNY, KRW, RUB, TRY, NGN, ARS, AUD, CHF, and GBP.
Omit log events.
Processing: Realtime
Comparing GoldRush’s Transactions API to RPC Providers
How to Track Wallets or Transactions with the GoldRush API
How to Get the Number of Transactions in a Block
Building Block Explorers (Part 1) - Multi-chain Block Transaction Explorer
Introducing Transactions V3 APIs
How to Get All Historical Transactions in a Block
Path Parameters
The chain name eg: eth-mainnet.
The requested block hash.
Query Parameters
The currency to convert. Supports USD, CAD, EUR, SGD, INR, JPY, VND, CNY, KRW, RUB, TRY, NGN, ARS, AUD, CHF, and GBP.
Omit log events.
Response
The timestamp when the response was generated. Useful to show data staleness to users.
The requested chain ID eg: 1.
The requested chain name eg: eth-mainnet.
List of response items.
The block signed timestamp in UTC.
The height of the block.
The hash of the block. Use it to remove transactions from re-org-ed blocks.
The requested transaction hash.
The offset is the position of the tx in the block.
Indicates whether a transaction failed or succeeded.
The sender's wallet address.
The address of the miner.
The label of from address.
The receiver's wallet address.
The label of to address.
b;The value attached to this tx.
The value attached in quote-currency to this tx.
A prettier version of the quote for rendering purposes.
The requested chain native gas token metadata.
Use contract decimals to format the token balance for display purposes - divide the balance by 10^{contract_decimals}.
The string returned by the name() method.
The ticker symbol for this contract. This field is set by a developer and non-unique across a network.
Use the relevant contract_address to lookup prices, logos, token transfers, etc.
A list of supported standard ERC interfaces, eg: ERC20 and ERC721.
The contract logo URL.
The gas spent for this tx.
The gas price at the time of this tx.
b;The total transaction fees (gas_price * gas_spent) paid for this tx, denoted in wei.
The gas spent in quote-currency denomination.
A prettier version of the quote for rendering purposes.
The native gas exchange rate for the requested quote-currency.
The details for the dex transaction.
The offset is the position of the log entry within an event log.
Stores the name of the protocol that facilitated the event.
Stores the contract address of the protocol that facilitated the event.
The protocol logo URL.
Stores the aggregator responsible for the event.
Stores the contract address of the aggregator responsible for the event.
DEXs often have multiple version - e.g Uniswap V1, V2 and V3. The version field allows you to look at a specific version of the DEX.
Similarly to the version field, fork_version gives you the version of the forked DEX. For example, most DEXs are a fork of Uniswap V2; therefore, fork = aave & fork_version = 2
Many DEXs are a fork of an already established DEX. The fork field allows you to see which DEX has been forked.
Stores the event taking place - e.g swap, add_liquidity and remove_liquidity.
Stores the address of the pair that the user interacts with.
Stores the address of token 0 in the specific pair.
Stores the ticker symbol of token 0 in the specific pair.
Stores the number of contract decimals of token 0 in the specific pair.
Stores the contract name of token 0 in the specific pair.
Stores the address of token 1 in the specific pair.
Stores the ticker symbol of token 1 in the specific pair.
Stores the number of contract decimals of token 1 in the specific pair.
Stores the contract name of token 1 in the specific pair.
Stores the amount of token 0 used in the transaction. For example, 1 ETH, 100 USDC, 30 UNI, etc.
Stores the amount of token 1 used in the transaction. For example, 1 ETH, 100 USDC, 30 UNI, etc.
Stores the wallet address that initiated the transaction (i.e the wallet paying the gas fee).
Stores the recipient of the transaction - recipients can be other wallets or smart contracts. For example, if you want to Swap tokens on Uniswap, the Uniswap router would typically be the recipient of the transaction.
The details for the NFT sale transaction.
The offset is the position of the log entry within an event log.
Stores the topic event hash. All events have a unique topic event hash.
Stores the contract address of the protocol that facilitated the event.
Stores the name of the protocol that facilitated the event.
The protocol logo URL.
Stores the address of the transaction recipient.
Stores the address of the transaction sender.
Stores the address selling the NFT.
Stores the address buying the NFT.
Stores the NFTs token ID. All NFTs have a token ID. Within a collection, these token IDs are unique. If the NFT is transferred to another owner, the token id remains the same, as this number is its identifier within a collection. For example, if a collection has 10K NFTs then an NFT in that collection can have a token ID from 1-10K.
Stores the address of the collection. For example, Bored Ape Yacht Club
Stores the name of the collection.
Stores the address of the token used to purchase the NFT.
Stores the name of the token used to purchase the NFT.
Stores the ticker symbol of the token used to purchase the NFT.
Stores the number decimal of the token used to purchase the NFT.
The token amount used to purchase the NFT. For example, if the user purchased an NFT for 1 ETH. The nft_token_price field will hold 1.
The USD amount used to purchase the NFT.
The price of the NFT denominated in the chains native token. Even if a seller sells their NFT for DAI or MANA, this field denominates the price in the native token (e.g. ETH, AVAX, FTM, etc.)
Stores the number of NFTs involved in the sale. It's quick routine to see multiple NFTs involved in a single sale.
The details for the lending protocol transaction.
The offset is the position of the log entry within an event log.
Stores the name of the lending protocol that facilitated the event.
Stores the contract address of the lending protocol that facilitated the event.
The protocol logo URL.
Lending protocols often have multiple version (e.g. Aave V1, V2 and V3). The version field allows you to look at a specific version of the Lending protocol.
Many lending protocols are a fork of an already established protocol. The fork column allows you to see which lending protocol has been forked.
Similarly to the version column, fork_version gives you the version of the forked lending protocol. For example, most lending protocols in the space are a fork of Aave V2; therefore, fork = aave & fork_version = 2
Stores the event taking place - e.g borrow, deposit, liquidation, 'repay' and 'withdraw'.
Stores the name of the LP token issued by the lending protocol. LP tokens can be debt or interest bearing tokens.
Stores the number decimal of the LP token.
Stores the ticker symbol of the LP token.
Stores the token address of the LP token.
Stores the amount of LP token used in the event (e.g. 1 aETH, 100 cUSDC, etc).
Stores the total USD amount of all the LP Token used in the event.
Stores the exchange rate between the LP and underlying token.
Stores the USD price of the LP Token used in the event.
Stores the name of the token going into the lending protocol (e.g the token getting deposited).
Stores the number decimal of the token going into the lending protocol.
Stores the address of the token going into the lending protocol.
Stores the ticker symbol of the token going into the lending protocol.
Stores the logo URL of the token going into the lending protocol.
Stores the amount of tokens going into the lending protocol (e.g 1 ETH, 100 USDC, etc).
Stores the total USD amount of all tokens going into the lending protocol.
Stores the name of the token going out of the lending protocol (e.g the token getting deposited).
Stores the number decimal of the token going out of the lending protocol.
Stores the address of the token going out of the lending protocol.
Stores the ticker symbol of the token going out of the lending protocol.
Stores the logo URL of the token going out of the lending protocol.
Stores the amount of tokens going out of the lending protocol (e.g 1 ETH, 100 USDC, etc).
Stores the total USD amount of all tokens going out of the lending protocol.
Stores the type of loan the user is taking out. Lending protocols enable you to take out a stable or variable loan. Only relevant to borrow events.
Stores the interest rate of the loan. Only relevant to borrow events.
Stores the wallet address liquidating the loan. Only relevant to liquidation events.
Stores the wallet address of the user initiating the event.
The log events.
The block signed timestamp in UTC.
The height of the block.
The offset is the position of the tx in the block.
The offset is the position of the log entry within an event log.
The requested transaction hash.
The log topics in raw data.
Use contract decimals to format the token balance for display purposes - divide the balance by 10^{contract_decimals}.
The name of the sender.
The address of the sender.
The label of the sender address.
The contract logo URL.
A list of supported standard ERC interfaces, eg: ERC20 and ERC721.
The address of the deployed UniswapV2 like factory contract for this DEX.
The log events in raw.
The decoded item.