log-flume VS ethereum-lite-explorer

Excluding State data, the team at Rivet.cloud has built Flume, which indexes everything into a Sqlite database. Flume offers a number of baked in RPC queries, but you can also open the sqlite database and run your own queries. I should caution you that for ETH mainnet, the database is about 1.6 TB.

I'd also point you to Flume, a project that already does this. I work for Rivet.cloud, and we use Flume to index blocks, transactions, receipts, and logs for faster querying. It can sync up over Websockets (very time consuming) or you can give it a synced Geth database and it can index it much more quickly.

Block explorers like Etherscan and EthVM maintain additional indexes that use a lot more space than a normal node to make everything efficiently queryable. My team has developed Flume which will index logs, transactions, receipts, and blocks into a relational database, but that database ends up being >1.25 TB without even having the Ethereum state trie. Queries are super efficient, but the tradeoff is a lot more disk space.

We also have an open source log and transaction indexer called Flume, which gives high performance responses to eth_getLogs queries, and supports more in-depth queries of log and transaction data than are supported through traditional Ethereum nodes.

Flume will load blocks, transactions, receipts, and logs into a sqlite database, from which it has a number of rpc queries, though locally you could connect to the sqlite database and run your own queries. It doesn't include state data, however.

Aleth Lite