Example
Usage Guidelines
- Specify a desired
eventType(eg:Swap,Mint,Burn, etc.) to suit your needs on any supported network and timeframe - Narrow results by specific network, token address, and combine with filters such as
priceUsdTotalfor more targeted results. - Note: Token transfer events are not supported
- Multi-hop transactions will show each intermediate transaction separately (see troubleshooting tip below for details)
Troubleshooting Tips
A single transaction is returning multiple buy & sell events for the same transaction (multi-hop). Is this expected and how can we simplify?
A single transaction is returning multiple buy & sell events for the same transaction (multi-hop). Is this expected and how can we simplify?
Yes this is expected behavior for a multi-hop transaction, where a maker will initiate a transaction from Token A -> Token B -> Token C, for example. We understand that Token B is likely of zero interest, however, it is still a legitimate transaction that we must index. Using the transaction hash to disambiguate on the client side is really the only way to attempt to simplify the swap down to just Token A -> Token C.
A token swap event was not returned with our query results, why?
A token swap event was not returned with our query results, why?
The transaction most likely occured on a protocol that we do not support. While we endeavor to support as many dexes as possible, including thousands of Uniswap forks, there are some we may not have yet. You can reach out to our team to inquire about specific exchanges you would like to see supported in a future update.
How do I determine which tokens were received vs sent for a given transaction?
How do I determine which tokens were received vs sent for a given transaction?
Look at the signs of amount0 and amount1 in the data field:
Negative amount = Token received (bought)
Positive amount = Token spent (sold)This rule is consistent for ALL transactions:
Positive = what they gave up (OUT of wallet)
Negative = what they received (INTO wallet)The eventDisplayType βBuyβ/βSellβ indicates the primary action from the userβs perspective (buying or selling the non-native token), while the amount signs show the actual token flows.
Negative amount = Token received (bought)
Positive amount = Token spent (sold)This rule is consistent for ALL transactions:
Positive = what they gave up (OUT of wallet)
Negative = what they received (INTO wallet)The eventDisplayType βBuyβ/βSellβ indicates the primary action from the userβs perspective (buying or selling the non-native token), while the amount signs show the actual token flows.
Returns: MakerEventConnection
Arguments
The maximum number of events to return.
The query filters to apply to the results.
The cursor to use for pagination.
The order to receive the token events. Can be
DESC (default) or ASC.