YellowScout Explorer

Basically Yellow uses state channels in many evm chains, the regular explorers will only show open/close transactions users can't see what's happening inside unless they use the yellow API, YellowScout Explorer fixes this problem by caching the data on a database with 2 cron jobs getting the data from websockets (testnet/mainnet) and displaying it in the Blockscout frontend.

I built a blockchain explorer by using the BlockScout frontend as a foundation, customizing and extending it to suit the specific requirements of my project. Rather than querying blockchain data directly from an api on the frontend, I set up a separate backend pipeline to handle data ingestion and processing more efficiently.

This backend system leverages WebSocket connections to listen for real-time blockchain events. A Go-based cron job continuously processes this incoming data, extracting relevant transaction, block, and contract activity. The processed data is then structured and stored in a PostgreSQL database hosted on Supabase for scalability and easy integration.

On the frontend, I customized the BlockScout interface to interact with my Supabase-hosted PostgreSQL database through RESTful API endpoints. This architecture allows for faster and more flexible data queries, improved performance, and better decoupling between the frontend and blockchain infrastructure.

The entire system provides an optimized and scalable solution for displaying blockchain activity, including real-time updates, historical lookups, and custom analytics, all within a user-friendly Next.js frontend.