What does an explorer profile update clarify?
An explorer profile update aligns the information people see on a token page with the project’s current identity. It can cover token details, a logo and social links on Etherscan, BscScan, Solscan or Tonviewer, depending on the platform’s available update process.
This is useful when a project has launched with incomplete public details, changed its branding, or needs to correct links that no longer represent its official channels. It is also a practical part of a broader verification and listing plan, rather than a substitute for one. For the wider landscape, see listings and verification.
Before commissioning work, decide what must change and what should remain untouched:
- Confirm the token contract address and network from a source controlled by your team.
- Compare the current explorer page against the project’s approved name, logo and official URLs.
- Identify the person who can confirm ownership or provide any platform-requested evidence.
- Flag any migration or rebrand so outdated details are not mistaken for the current token.
If an update is connected to a contract change, coordinate the explorer request with the contract migration and rebranding update work. That keeps the explanation consistent across public references.
How do Etherscan, BscScan, Solscan and Tonviewer updates differ?
The target explorer determines the submission route, the fields available for editing and the evidence the project may need to provide. We review each requested destination separately instead of assuming one form or approval applies everywhere.
The scope can include a token logo, public token information and links to the project’s website or social channels where those fields are available. Etherscan and BscScan cover the relevant EVM explorer pages; Solscan and Tonviewer serve different chain ecosystems. The project should therefore confirm the exact contract or token address and chain before any information is prepared.
A useful handoff list is:
- Explorer name and direct token-page URL, if the page already exists.
- Exact token address, copied from a trusted project-controlled source.
- Approved display name, concise project description and logo file.
- Official links that open correctly without redirects to unrelated pages.
- A contact who can respond if an explorer requests clarification or ownership evidence.
For projects also updating tracker profiles, keep the public description and social destinations aligned with the DEXTools and DEXScreener profile update scope. This avoids preparing separate, conflicting versions of the project identity.
What should the explorer update package contain?
A strong package gives the reviewer clear, consistent information and makes it easy for your team to approve the exact details being submitted. We check the assets and links as a set, not as isolated fields.
The final contents depend on the explorer’s available fields and request instructions. As a preparation standard, provide a clean logo that represents the token, a short factual description, and only official destinations. A link should resolve to the project’s real channel or website; a polished-looking URL is not enough if it leads to stale or incomplete information.
MediaStrategy uses a kickoff checklist to catch mismatches before submission. It records the chain and address, approved token naming, selected logo, current links, requested changes and the person authorized to sign off. You review that package before it is sent, so the team has one approved source of truth.
If the logo also needs to appear in a wallet or token list, treat that as a separate destination with its own requirements. We can coordinate that alongside the explorer work through wallet logo and token list inclusion, while keeping the asset version consistent. For a project with an established profile elsewhere, we can also compare the requested explorer details against its current public references before final approval.
How does MediaStrategy manage the update from kickoff to handoff?
We manage explorer updates as a controlled submission: confirm the requested changes, prepare one approved package, coordinate the request and report what happened. A senior account lead handles the working thread, so questions and platform feedback do not become scattered across team members.
The usual sequence is straightforward:
- Scope: You identify the explorers and token pages in scope, along with the details to add or correct.
- Review: We check the address, logo, description and official links against your supplied sources and flag inconsistencies for your decision.
- Approval: Your authorized contact confirms the final package before it is submitted.
- Coordination: We follow the relevant explorer process and relay any request for clarification or additional material.
- Handoff: You receive a concise status note showing destinations handled, submitted information and any outstanding platform response.
The schedule begins once the project supplies usable materials and approves the package. The overall wait then follows the response and review process for each explorer, so projects targeting more than one platform should plan around separate status updates rather than assume a single shared review. If a request is returned with questions, we help organize the response using the approved project information.
What can affect publication on a token explorer?
Publication is controlled by the explorer’s own submission, review and editing process, so the project should plan for platform-specific feedback. Our work is to prepare and coordinate the agreed update, keep the record of what was submitted, and help respond to requests using the project’s approved materials.
Etherscan, BscScan, Solscan and Tonviewer may differ in the information they display and the evidence or review steps they request. Their decision to accept a change, the fields they expose, and when an accepted edit appears are outside our control; we promise delivery of the agreed preparation and coordination, not an explorer’s approval or display decision.
Before kickoff, make the request easier to assess by checking that:
- The token address and selected explorer refer to the intended asset.
- The logo and description are approved and do not imply an affiliation the project cannot substantiate.
- Each social link is official, accessible and maintained by the project.
- A responsible contact can provide clarification if asked.
Send us the token address, target explorer pages and the changes you want. MediaStrategy will return a scoped checklist for your approval and then coordinate the agreed submission.
Prices
| Service | Price | Quote |
|---|---|---|
| Explorer Profile Updates | from $220 / project |
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
- Share the token detailsSend the chain, token address, target explorer pages and requested changes. Include the project’s official website and social destinations.
- Review the materialsWe compare the supplied details and logo against the requested updates, then flag missing or inconsistent items for your team.
- Approve the packageYour designated contact confirms the final token information and links before we proceed with the explorer requests.
- Coordinate and reportWe handle the agreed submission coordination, relay platform questions and provide a status note for each destination.
- Complete the handoffYou receive a record of work completed and any remaining response or action needed from the project or explorer.
Frequently asked questions
Which token explorers can you support?
We coordinate token info, logo and social link update work for Etherscan, BscScan, Solscan and Tonviewer. Share the token address and the exact explorer pages you have in mind so we can confirm the requested scope and prepare for each destination separately.
What does my team need to provide?
Provide the chain and token address, current explorer page links where available, the approved logo, token name and description, and official project URLs. You should also name a contact who can approve the package and answer any platform questions about the project or its information.
Can you update a logo after a rebrand?
Yes, we can coordinate a logo and token information update as part of a rebrand. Share the new approved identity, the explorer pages to change and any context needed to distinguish the current token from earlier project details. If the contract also changed, include that information at kickoff.
How long does an explorer token update take?
Preparation starts after we receive the required materials and your team approves the package. The time to publication then depends on each explorer’s review and response process, including any follow-up it requests. We provide status updates rather than promise a publication time controlled by the platform.
Can you guarantee that an explorer will publish the update?
No. Each explorer controls its own review, evidence requests, available profile fields and publication decision. We can commit to preparing and coordinating the agreed submission, keeping you informed and helping organize a response using your approved information, but not to approval or a specific display outcome.
Is an explorer profile update the same as a tracker listing?
No. An explorer update concerns information displayed on a chain explorer’s token page. A tracker listing is a separate platform request with its own scope and process. If you need both, we can coordinate the explorer work with a relevant CoinMarketCap listing or CoinGecko listing project.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…