Avalanche is a Layer 0 ecosystem made up of three core Blockchains each optimized for specific tasks within the network. AVAX, the native utility token of the Avalanche Network is used to pay fees for transactions, delegate to secure the network, as well as pair with other assets or stable coins to participate in DeFi products. - The Tie

Avalanche was developed by researchers from Cornell University led by Emin Gün Sirer and doctoral students Maofan "Ted" Yin and Kevin Sekniqi. On September 2020 Avalanche and Avax launched with Ava Labs behind - Wikipedia

These terms are really important to understand the data showed, so let me explain using my own words and the data from flipside to answer these questions:

• Contract is the short name for "Smart Contracts" and basically these are addresses that execute commands in the Avalanche Network to make complex activity such as swaps, bridges, Liquidity Pools etc.
• dApp is a group of Smart Contracts used by an "Application", for example Trader Joe v1 Avalanche contracts are these.

So we can make an analogy such as "a contract is like a Tree and a the dApp is like the Forest".

Now, let me explain something really important:

• Basically every transaction can execute more than 1 smart contract, and because of that every log of activity made by the transactions is registered in the events table of Avalanche on FlipsideCrypto.
• What happens when 1 transactions calls more than 1 smart contract? How you can distribute the gas fee spent by all the smart contracts involved in 1 transaction?.

That problem leds me to the following part that is the Accuracy of the Data.

Because is impossible to distribute the transaction fee of a single transaction in all the smart contracts involved, I'll interpret that every smart contract behind that transaction is responsable for the same amount of gas usage and $AVAX fee, once.

And that lead us to the next problem, Inflated Results this problem arises after joining the table "Event" with the "Transactions" table, because of that if the same smart contract was used more than once per transaction, then the sum of transactions fees will add all the times that smart contract was called per transaction.

To understand better let me show an example:

• Using the correct method I'll achieve that the smart contract is considered once per transaction hash, as we can see Count(distinct a.tx_hash) is the same as count(*)
• Using the incorrect method will inflate too much the numbers because some transactions will be counted more than once.
• Because of that the top 5 contracts by $AVAX Fees are completely different in both scenarios.

I firmly believe that the results using the correct method are more accurate than doing the incorrect method.

But overall the following tabs will the following accuracy:

• Overall activity Tab doesn't have this problem and all the data here is completely accurated.
• Contract Tab have the problem that a single transaction will be considered multiples times but once per smart contract involved, inflating the results but achieving the Correct Method.
• dApp Tab have the same contract problem, and besides only labeled contract addresses will be considered for the top dApps as these are the only we can really know the dApp involved, additionally the Wrapped Avax Contract will not be included here because all relevant activity about it is showed in the Contract Tab

• With the Days Parameter you can select the Timeframe for all the results!, (Days = 30) means the last 30 days.