Rather, they show the number of hashes stored in the Storage Contracts. The number of hashes stored is less than the number of individual transactions because individual transactions can be "batched", and stored in the same IPFS document, resulting in a shared hash.
Both numbers are interesting - the hashes stored are useful for understanding protocol fee burn and the individual transactions are useful to understand how frequently the protocol is used.
Solution
[ ] Create a public dashboard that shows individual transactions.
[ ] Segment transactions by Builder to help understand which apps in the RN ecosystem are contributing the most protocol usage
Problem
The existing public dashboards don't show individual transactions.
Rather, they show the number of hashes stored in the Storage Contracts. The number of hashes stored is less than the number of individual transactions because individual transactions can be "batched", and stored in the same IPFS document, resulting in a shared hash.
Both numbers are interesting - the hashes stored are useful for understanding protocol fee burn and the individual transactions are useful to understand how frequently the protocol is used.
Solution