you can see nothing show pls hep me

When you search something in the V2 search bar, the returns results based on the aliases of the data tables. e.g: if you type "erc20 transfer" you will get the result, but if you type in "transfers_ethereum.erc20" which is the exact name of the table as used in the query the search bar returns nothing. This is annoying when navigating the indexed databases as I remember the tables that I use by their proper names and not aliases. This is especially tricky for decoded functions which can have lengthy names which the alias does not reflect.

Solana programs may use base58 for data encoding, to parse program data it'd be of use to have base58 decode method to dig in more to build more robust dashboards (for Solana)

In DuneSQL, interval '1' week does not work. The suggested workaround is to use '7' day, but this also causes datatype failures in the following code (where time granularity is an input - we want calendar months, so '30' day does not suffice) CASE WHEN '{{Time Period}}' = 'week' THEN interval '7' day WHEN '{{Time Period}}' = 'day' THEN interval '1' day WHEN '{{Time Period}}' = 'month' THEN interval '1' month END

Given a data input: Count how many zeo bytes Count how many nonzero bytes Calldata gas = 16 nonzero_bytes + 4 zero+bytes Formula in DuneSQL format is here: 16 * ( bytearray_length(data) - (length(from_utf8(data)) - length(replace(from_utf8(data), chr(0), ''))) ) --nonzero bytes + 4 * ( (length(from_utf8(data)) - length(replace(from_utf8(data), chr(0), ''))) ) AS calldata_gas It could be formatted like get_calldata_gas(data)

Something like labels.get(...) would be amazing. Or have the full labels table available in v2 so we can join it in queries.

Using Select * to join Tables only brings in 1 column even when they aren't Identical. For instance, connecting ERC20 Transfers to ERC20 Tokens brings in the contract_address column from ERC20.Tokens which doesn't have every ERC20 Token. Its a difficult to spot problem and a very common table join for new users. https://dune.com/queries/2349030

In Dune v2.0, a lot of abstractions now use string instead of Bytea. In SQL strings are case sensitive, so I have to format every single txhash, and address that I use because the data tables are strings now instead of bytea.

Would be great if the Solana DB had access to dune_user_generated similar to ETH DB

When I run a query more than once, I get different results in this query. Moreover, I do not change the request, I run the same one. https://dune.com/queries/1686953