In the above picture, the Settings Page is dynamically populated with the available Block Explorers in the system. This will go a long way to speeding up the development of new cryptos and their associated block explorers. One major thing this also allows is the ability to present user-defined configuration properties, like the API Key displayed in the picture. These will also be dynamically populated, depending on if a specific Block Explorer has any config properties to begin with. The design I've implemented provides a robust way for a Block Explorer to define a lot of different pieces here, including a 'help text' that, if defined, will display a small (?) icon. When clicked by the user, the 'help text' is presented as a toast.
A lot more work is still needed, but this represents a lot of good progress.
Began prototyping the UI sections on the Settings Page that will eventually be populated by the present of active block explorer API implementations.