Explorer token info and logo update service

What does an explorer token info update cover?

An explorer token info update is a request to present project details alongside a token or contract page. The exact fields and submission route vary by explorer, but the practical goal is consistent: help users identify the asset and find the project's official information without guessing.

We support submissions for Etherscan, BscScan, Solscan and Tonviewer. Depending on the platform and the asset, the work can include preparing or checking a logo, token description, website and social links, then organizing the information for submission. We also help the team identify gaps before the request is sent.

This service is useful when a token page is missing a project logo, displays incomplete details, or points users to outdated social profiles. It can also help when a team is preparing a launch and wants its public information ready to submit. For a broader overview of platform listings and verification options, see Listings and verification.

A helpful outcome is not just a submitted form. It is a coherent set of details that match the project’s public identity and can be checked against the token or contract address. We keep the scope clear so the team knows which explorer is included and what information still needs to come from its side.

Which explorer should receive the token information?

Start with the explorer that users already visit to inspect the token’s on-chain activity. The right destination usually follows the network where the token exists, rather than the project’s preferred branding or marketing calendar.

Etherscan is relevant for Ethereum token pages, BscScan for BNB Smart Chain, Solscan for Solana, and Tonviewer for TON. If a project operates across networks, each relevant token or contract may need its own information review and submission. We confirm the requested explorer and asset before preparing materials, so details are not sent to the wrong page.

Before requesting an update, the project team should gather:

• The exact token or contract address copied from a trusted source.
• The official project name and a concise, factual description.
• The current logo file and the destination where it should appear.
• Website and social URLs that resolve to project-controlled pages.
• Any ownership or project evidence the explorer’s process asks the team to provide.

If information is changing as part of a contract migration or rebrand, align explorer updates with the wider record changes. Our contract migration and rebranding updates service can help coordinate that work. If you are unsure which network page is the priority, send the contract address and launch context first; we can confirm the requested scope before submission.

How do we prepare a clean explorer submission?

A clean submission begins with one verified source of truth for the token and project details. We compare the supplied address, name, description, logo and links for consistency, then flag missing or conflicting items before the request moves forward.

The team should provide a logo that represents the project and remains legible when displayed small. Social links should lead directly to official, active project pages, not redirects or third-party profiles. Descriptions should be factual and easy to understand; avoid unsupported claims, ambiguous ticker references and wording that does not match the project’s public materials.

Our preparation typically includes:

• Confirming which explorer and token page are in scope.
• Reviewing the supplied information for consistency and obvious omissions.
• Organizing logo and project links in a submission-ready format.
• Checking that the team can provide requested evidence or respond to follow-up questions.
• Recording what has been submitted and what remains under review.

For a token that also needs a visible profile on market discovery tools, explorer updates are separate from profile work on DEXTools or DEXScreener. See DEXTools and DEXScreener profile update for that scope. Keeping these tasks distinct helps teams understand where each piece of information is meant to appear and avoids treating one platform’s submission as an update everywhere.

What happens after the explorer update is submitted?

After submission, the explorer’s own process determines whether the requested information is reviewed, accepted and displayed. Our role is to prepare the materials, submit or guide the submission as agreed, track the status available to the team and help respond to actionable requests for clarification.

Timing starts with project readiness. If the address, logo, links and supporting information are complete, preparation can begin without waiting for the team to resolve basic inconsistencies. If details are missing or a platform asks for more information, the schedule extends until the team supplies what is needed and the explorer completes its review. We do not replace the project’s authorized contact where the platform requires the team to verify control directly.

The working sequence is straightforward:

1. Confirm the explorer, token address and requested changes.
2. Collect and check project information and logo assets.
3. Prepare the submission and identify any required team action.
4. Submit or guide the team through submission, as agreed.
5. Track the available status and share the outcome or next action.

Teams that also need circulating supply information reviewed should treat that as a distinct verification task. See circulating supply verification to compare the scope. We provide a clear handoff after each explorer request so the team can see what was supplied, what is pending and what was actually confirmed.

What can affect approval on Etherscan, BscScan, Solscan or Tonviewer?

Each explorer controls its own eligibility checks, evidence requirements, moderation decisions and display behavior. We can prepare an accurate request and deliver the agreed submission work, but we cannot promise that an explorer will accept every logo or information change, publish it by a particular time, or display it identically across every page and interface.

A request may need more work when the submitted details conflict with information already visible on-chain, links do not establish a clear connection to the project, or the platform asks for evidence the team has not provided. A logo can also be delayed if it does not meet the explorer’s current requirements. These are reasons to check the platform’s own instructions at the point of submission rather than relying on an old checklist.

To reduce avoidable back-and-forth, assign one person to approve the final name, description, links and logo. Keep a copy of the exact submitted version, and make sure that person can respond if the explorer asks a follow-up question. If the token recently changed its name or moved to a new contract, explain that context and coordinate related updates instead of presenting inconsistent records.

We will report the status we can verify and separate completed agency work from decisions made by the explorer. That distinction matters: the agreed deliverable is the preparation and submission support, while approval and final display remain with the platform.

How does explorer information fit into wider token visibility?

Explorer information is one part of a token’s public record; it does not replace listings, market profiles or wallet display work. A logo and official links on an explorer can make its token page more useful, while separate platforms may require their own submissions, eligibility checks and materials.

Choose the next task based on where users encounter a gap. If the project needs an asset logo to appear in supported wallet or token-list interfaces, review wallet logo and token list inclusion. If the priority is an exchange or data-platform record, compare the relevant options in Listings and verification. These are related goals, not one combined update.

For a practical handoff, keep a shared record with the canonical token address, approved project name, current logo, official website and social URLs, plus the status for each platform. Note when a value changes and who approved it. This prevents one explorer submission from using an old link while another service works from a newer version.

Our scope is agreed before work begins: which explorer or explorers are included, what information is being updated, what the team must supply, and how we will report progress. The starting price is from $180 / project. If a request involves several networks or a broader verification need, contact us with the addresses and desired changes so we can confirm the work before proceeding.

Prices

Starting prices in USD. Custom bundles and volume discounts on request. Payment in USDT, USDC, BTC, ETH, SOL, TON or your project token.

How it works

1. Confirm the targetShare the explorer, network and exact token or contract address. We confirm which page and requested changes are in scope.
2. Gather project materialsProvide the approved logo, description, website and social links, along with any evidence the platform requests.
3. Check and prepareWe review the details for consistency, identify missing items and organize the submission materials.
4. Submit and coordinateWe submit or guide your authorized team through the explorer’s process, then help with relevant follow-up questions.
5. Report the outcomeWe share the status we can confirm and distinguish completed work from any decision or action still pending with the explorer.