Explorer and indexer now match the chain's real history window

Satsuma's block explorer, built in the satsuma-explorer repository, now describes the chain's history limit as it really is: nothing before block 4,814,594, reached on 2026-10-16, then a rolling 30 days, or 1,296,000 blocks. The older wording about only around 255 blocks of history is gone. When a block or transaction cannot be found, the explorer now says so with the new limit, and the block message names the oldest block the node still serves. The README, AGENTS.md and llms.txt files were updated to match. The change is merged.

The indexer, the background program that copies blocks into the explorer's database, now asks for blocks 10 per request and fetches the receipts for each chunk in one batch. Only the request for the latest finalized block is still a single call. Its look-back is now 30 days minus about 3 hours of margin, and never earlier than block 4,814,594.

The indexer runs as a Worker, a small program on a hosted serverless platform that starts on a schedule; each run is capped at 45 RPC requests to stay under the platform's per-run subrequest limit. The cap was set without knowing which plan the hosting account is on. After the Worker was redeployed, one scheduled run moved its position from block 4,816,346 to 4,816,376, about 30 blocks a minute, with no gaps.

The 45-request cap stays where it is until the hosting plan is known.