4 explorers, one token info and logo update

1 contract address opens the explorer update

First input: the contract address for each target page. We match it to the explorer page and the fields you want changed.

4 destinations can mean 4 separate page checks. One explorer page does not update another page automatically. We list each chain and address separately. Then we confirm which visible fields have an available update route. That keeps the request tied to the correct token page.

For a wider view of exchange and tracker destinations, start with listings and verification. This service stays focused on the explorer page and the project details shown there.

How do 5 checks move the request to submission?

5 checks take the request from the live page to a documented handoff. We flag missing or conflicting details before materials are prepared.

1. Match the destination: confirm each chain, address and explorer page against the information you send.
2. Mark requested fields: record whether the change concerns a logo, description, website or social link.
3. Check project sources: compare the requested details with your official website and social pages.
4. Assemble the request: organize the logo, approved copy, links and any supporting material required by the available route.
5. Confirm the outcome: check the public page again and note what changed or remains open.

You keep control of project accounts and any ownership credentials. We do not need private keys or seed phrases. Your authorized representative handles any direct account action. We guide the submission and track the visible result.

For a contract change or rebrand, coordinate the explorer request with contract migration and rebranding updates.

6 items in the profile pack

6 items make the requested change easy to check. They cover the address and target page. They also cover approved profile details and supporting files or links. We organize the pack around fields available on the selected explorer.

• Address: the exact contract address and chain for every target page.
• Logo: original artwork that stays clear at a small display size.
• Description: final project text approved by your team.
• Website: the official URL, opened to confirm it reaches the intended destination.
• Social links: official account URLs checked for typos and redirects.
• Prior correspondence: any existing request or explorer response that may affect the next submission.

File requirements vary by destination, so use the selected explorer’s current instructions. We do not assume one image dimension fits every route. The check also flags artwork that includes unrelated project or platform marks.

If a wallet display needs its own logo or token-list review, see wallet logo and token list inclusion.

What changes across Etherscan, BscScan, Solscan and Tonviewer?

4 named explorers mean 4 destination checks. The destination determines which visible fields and update route we check. We review each relevant page. We do not treat four explorers as one shared form.

Each explorer decides whether a submitted logo or social field qualifies. It sets the evidence it needs and when an accepted change appears. We cannot promise approval or a publication time. We do promise the agreed preparation, submission support and page check.

For profile changes on market trackers, use the separate DEXTools and DEXScreener profile update service. For broader tracker destinations, see other crypto tracker listings.

Send us the 5 source items for a clean handoff

5 source items help us identify the right page and prepare a focused request. Send the approved version your team wants displayed. Avoid draft copy that may change during submission.

• Chain and address: list every chain and exact contract address.
• Explorer pages: send the live page link for each requested update.
• Logo file: include the original artwork in a usable format.
• Approved details: provide the final description, website and social URLs.
• Earlier requests: attach any explorer reply or existing submission record.

We compare the live page with your approved information. Then we send back the route and field checklist. If supply details also need separate evidence, see circulating supply verification. A tracker application is separate from an explorer profile change. We can map those destinations independently.

Send: chain, exact address, target page, logo source and official URLs. We reply with the relevant route and a written quote.

How it works

1. Send the page referencesProvide the chain, exact address, explorer page and official project URLs. Add any earlier request or response.
2. Confirm the requested fieldsWe compare the live page with the logo, text or links you want changed. We flag missing details before preparing the request.
3. Prepare the profile materialsWe organize the approved logo, description, links and supporting material for the selected route.
4. Coordinate the submissionYour authorized representative handles any direct account action. We guide the request and help address follow-up questions.
5. Check the public pageWe revisit the explorer page and send a status note showing visible changes and open items.