Why update token information on a blockchain explorer?
An explorer profile gives users a public place to check a token’s identity alongside its on-chain record. A consistent name, logo and set of social links can make it easier for people—and systems that summarize public information—to connect the token with the right project. It is a useful part of discoverability, not a substitute for a clear website or reliable project communications.
The service is for teams that have launched a token, changed their public identity, or found that an explorer page is missing or out of date. It is also relevant when social accounts or a website have moved and old links no longer represent the project.
We start by defining the exact scope:
- Which chain and explorer pages need an update
- Which contract address identifies the token
- Which name, logo and official links should appear
- Whether this is a first submission or a correction to existing information
That scope prevents teams from sending inconsistent versions of the project identity to different destinations. For a broader overview of directory and verification work, see listings and verification.
How do Etherscan, BscScan, Solscan and Tonviewer updates differ?
The project information may be similar across explorers, but each destination has its own interface and submission process. We prepare the information for the explorer you select rather than treating one completed profile as proof that every other explorer has been updated.
Etherscan and BscScan are relevant for projects on their respective networks; Solscan and Tonviewer serve Solana and TON token pages. Before submission, we confirm the requested explorer, the token address, the current project identity and the links the team wants to publish. We then check the explorer’s current instructions and organize the materials for that route.
The working file keeps the details easy to compare:
| Item | Preparation check |
|---|---|
| Token address | Confirmed against the project’s chosen on-chain record |
| Name and description | Supplied in the project’s approved wording |
| Logo | Correct asset version and usable file supplied by the team |
| Social links | Official destinations open and match the project identity |
This approach is especially important after a contract migration or rebrand. If the token identity has changed, coordinate explorer updates with contract migration and rebranding updates so public references do not conflict.
What should your team prepare before submitting?
A complete, consistent set of materials makes the submission easier to review and reduces avoidable clarification. Before kickoff, collect the contract address, the preferred token name, a concise project description if requested, the approved logo file and the official website and social URLs.
Our named pre-submission review compares those items against one project-approved source of truth. It checks that the address is the one the team intends to update, that the logo supplied is the current approved asset, and that each social link leads to an official project destination. We also flag mismatched naming or links that appear to point to an older identity before anything is sent.
For a smooth handoff, send:
- The chain and explorer pages in scope
- The token address copied from the project’s confirmed records
- Final logo and wording, not draft alternatives
- Official URLs with access available for verification
- A contact who can approve corrections promptly
If several team members hold different versions of the logo or project description, resolve that internally first. When a token logo also needs work beyond explorer pages, review wallet logo and token list inclusion. For updates to other market profiles, see DEXTools and DEXScreener profile update.
What happens after the explorer submission is prepared?
You receive a clear record of what is ready, what has been submitted and whether a follow-up is needed. The work moves from scope confirmation to material review, submission coordination and status reporting; the sequence keeps the team aware of the next action rather than leaving a request untracked.
After kickoff, we confirm the target explorer pages and gather the approved content. We check the package, prepare it according to the current submission route, and coordinate the submission with the project contact. If the explorer requests a correction or additional information, we relay the specific request so the team can approve a response.
The handoff includes the agreed submission details and a status summary. Where multiple explorers are in scope, each destination is tracked separately; an update on one explorer does not stand in for a submission to another. If profile information is part of a wider verification plan, connect this work with circulating supply verification or the wider listings and verification plan.
To keep the work moving, appoint one person who can confirm the final wording and respond to follow-up questions. That avoids competing instructions and gives the project a single accountable owner for public token information.
What can explorer review change?
For Etherscan, BscScan, Solscan and Tonviewer, the explorer—not our team—sets the applicable submission requirements, decides whether the supplied token information, logo and social links meet them, and controls whether and when a profile change appears. A request may require the project to clarify ownership, provide additional details, correct an asset or adjust a link; we will identify the requested action and coordinate your response, but the explorer makes the final decision. Before kickoff, we check that the requested update matches the selected chain and token address, keep the approved materials together, and report each destination as prepared, submitted, awaiting project input, or reviewed; this makes the status actionable without implying approval before publication.
How does an explorer profile support AI and search visibility?
A consistent explorer record can strengthen the public information available about a token, giving users a reference that aligns with the project’s own website and social channels. That consistency is useful when people search for the token or when AI tools assemble an answer from accessible public sources, but an explorer update alone does not determine what those systems show.
Treat the explorer page as one component of a wider identity system. Use the same approved project name and logo across the website, social profiles, token directories and explorer submissions. Keep official links current, and make sure your own channels explain the project in clear, direct language. When the goal is broader discoverability in AI-generated answers, connect the profile work with AI search visibility.
A practical check after publication is to open each updated explorer page and compare it with your approved source of truth. Confirm the visible name, logo and links, then record any outstanding change by destination. We can provide that status summary as part of the agreed scope. Send us the chain, contract address, target explorer and approved assets; we will return a scoped plan and the first materials checklist.
Prices
| Service | Price | Quote |
|---|---|---|
| Explorer Profile Updates | from $190 / 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
- Confirm scopeTell us the chain, contract address and explorers you want updated. We map each target page separately.
- Collect approved materialsShare the final token name, logo, project wording and official social links. One project contact confirms the source of truth.
- Run the pre-submission reviewWe compare the address, identity assets and destinations, then flag inconsistencies for your approval before submission.
- Prepare and coordinate submissionsWe organize the materials for the applicable explorer process and coordinate the agreed requests.
- Report status and follow-upsYou receive a destination-by-destination status summary and any explorer request that needs your response.
Frequently asked questions
Which explorers can you help update?
We coordinate token information, logo and social-link updates for Etherscan, BscScan, Solscan and Tonviewer. Tell us the chain and target pages when you contact us; we will confirm the scope and materials needed for each destination.
What do you need from us to start?
Send the token contract address, the chain, the explorer pages to update, the approved logo and the official website and social links. A project contact should also be available to confirm the final wording and respond if an explorer requests clarification.
How much does an explorer token information update cost?
The starting price is from $190 / project. The final scope depends on which explorers and token pages need attention and what preparation is required. Share your target pages and materials so we can confirm the work included before kickoff.
How long does a token explorer update take?
Preparation starts after we receive the required project details and approved assets. The overall timing also includes the explorer’s own review and any follow-up it requests, so we provide status as the submission progresses rather than promise a fixed publication date.
Can one explorer update automatically change the other pages?
No. We scope Etherscan, BscScan, Solscan and Tonviewer destinations separately, and coordinate each agreed submission through its applicable process. Tell us every explorer where the project needs an update so none are assumed to be covered by another request.
Can you guarantee that the explorer will publish our logo and links?
No. The explorer controls its requirements, review decision and publication timing. We can prepare the agreed materials, coordinate the submission and help respond to a request for clarification, but we cannot make the explorer approve or publish a profile.
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…