# Activating free trial package
Source: https://docs.seitrace.com/api-reference/activating-free-trial-package
Experience our free plan to explore and enhance your product effortlessly. Enjoy valuable benefits and discover the full potential of our services at no initial cost. Get 90 days of free access to our API services. You won’t be charged until you decide to upgrade to a paid plan.
## Activating the Free Trial Package
* **One-Time Activation**: The free trial can be activated only once. Once a paid package is purchased or a trial has already been activated, reactivation is not possible.
* **Email Restrictions**: Each email type can activate the free trial only once. For example, if `contact@seitrace.com` activates the trial, `contact+test@seitrace.com` (an extended email for the original email: [contact@seitrace.com](mailto:contact@seitrace.com)) cannot.
## How to Activate a Trial Package
1. Log in to your account at [Seitrace.com](http://Seitrace.com).
2. Navigate to the Insights page: [https://seitrace.com/insights](https://seitrace.com/insights)
3. Scroll down to the "Free Trial" section.
4. Click on the "Get started now" button.
5. Confirm the activation of your trial package when prompted.
6. You will see a success message once the activation is complete.
After activation, you can access the API Keys management section.
In the API Keys management, you can create new API keys for use with the service.
Generate API keys for your Seitrace Insights account in a few simple steps.
# Create your API keys
Source: https://docs.seitrace.com/api-reference/create-your-api-keys
Generate API keys for your Seitrace Insights account in a few simple steps.
## Creating API Keys
Follow these steps to generate API keys for your Seitrace Insights account:
1. Navigate to your Profile and select "API Keys"
2. Click the "Add API Key" button
3. In the popup window, enter your "App name"
4. Click "Create API Key"
5. Copy the generated key for use in your application
## **Important Notes:**
* There is a limit of 3 API keys per user account
* If your API credits expire or are exhausted, your account reverts to "Regular" status
* API calls made with keys from a "Regular" account will cease to function
Remember to store your API key securely and never share it publicly.
Read our Insights Docs: [https://seitrace.com/insights-docs](https://seitrace.com/insights-docs)
# Insights (APIs) docs
Source: https://docs.seitrace.com/api-reference/insight-docs
# Introduction
Source: https://docs.seitrace.com/api-reference/introduction
Seitrace Insights is an API service that empowers your applications with the most reliable and comprehensive Sei Network Data API. Access real-time data from the leading Sei Network Explorer.
You can access Seitrace Insights to explore & try our free plan to explore and enhance your product effortlessly.
## Key Features
* **API Credit System**: Users purchase API credits to utilize the service. The credit has an expiration date.
* **Credit Packages**: Users can buy additional credits in packages to extend their usage & exprie date.
* **Expiration and Exhaustion**: Once credits expire or are exhausted, users revert to regular status and cannot access the API until credits are replenished.
## Packages
* **Free Trial**: A 90-day trial package for new users.
* **Paid Packages**:
* Insights 30D
* Insights 90D
* Insights 180D
* Insights 360D
* Custom packages are available through private deals.
## Getting Started
Explore and enhance your product effortlessly with our free trial plan.
Unlock valuable benefits and discover the full potential of our services.
Generate API keys for your Seitrace Insights account in a few simple steps.
Find detailed guides and resources to help you make the most of your Insights features.
# Purchasing an insights package
Source: https://docs.seitrace.com/api-reference/purchasing-an-insights-package
Unlock valuable benefits and discover the full potential of our services.
## Purchasing an Insight Package
To purchase an Insights package, follow these steps:
* Log in to your [Seitrace.com](http://Seitrace.com) account.
* Navigate to [https://seitrace.com/insights](https://seitrace.com/insights).
* Scroll down to the "API Self-Checkout" section.
* Select the plan that best fits your needs.
* Click "Get Started" on your chosen plan.
* Review the payment information carefully.
* Click "Confirm" to proceed with your purchase.
**Once confirmed, we will receive your information and contact you via email with instructions for payment.**
## **Payment methods**
In the initial phase, we support cryptocurrency payments. You can transfer funds to our company's wallet on the following networks:
* TRON
* Ethereum
* Polygon
* SEI
Supported currencies:
* USDC
* USDT
## **After payment**
Upon successful payment verification, we will:
1. Activate your chosen package.
2. Notify you via email.
You can then start using the API by creating your API keys in your account dashboard.
Generate API keys for your Seitrace Insights account in a few simple steps.
# 404 tokens
Source: https://docs.seitrace.com/assets/404-tokens
Doc coming soon
# Token details
Source: https://docs.seitrace.com/assets/fungible-tokens/token-details
The Token details page provides comprehensive information about a specific token on the SEI blockchain. This page supports both regular tokens and tokens with pointers.
## **Basic information**
The Token details page includes the following basic information about the token:
* **Price**: The current price of the token.
* **Full diluted market cap**: The market capitalization of the token.
* **Max total supply**: The maximum total supply of the token.
* **Holders**: The number of addresses holding the token.
* **Transfers**: The total number of transfers made with the token.
* **Contract information**: Details about the token contract, indicating whether it is an original or a pointer or just the normal token without pointer.
* **Original contract address**: The address of the original contract.
* **Pointer contract address**: The address of the pointer contract, if applicable.
* **Decimals**: The number of decimal places the token supports.
## **Token Transfers List**
Display a list of recent token transfers,
## **Token Holders**
The token holders section displays a list of addresses holding a specific token on the SEI blockchain. The display adapts depending on whether the token uses pointers or not.
* **Without pointer**: If the token does not include a pointer, it shows only one type of address (either EVM or Native SEI).
* **With pointer**: If the token includes a pointer, it shows both the EVM and Native SEI addresses of the owner.
## **Contract information**
Provide detailed information about the token contract
# Fungible tokens
Source: https://docs.seitrace.com/assets/fungible-tokens/tokens
The SEI blockchain supports various standards for fungible tokens across both EVM and Native SEI environments.
## **Supported Token Standards**
* **EVM**: ERC-20
* **Native SEI**:
* CW-20
* Native Token (SEI)
* IBC Tokens
## Tokens
The Tokens page provides an overview of all fungible tokens on the SEI blockchain, including those on both EVM and Native SEI. This page allows users to explore and view details about each token.
**Key features**
* **Token list**:
* Display a comprehensive list of fungible tokens available on the SEI blockchain.
* Each row in the token list includes the following information: Token & its address, the pointer/original of that token, type of token, price, Circulating market cap and the number of holders.
* **Filter and search**: Users can filter tokens by EVM/Native SEI and search for specific tokens by name or symbol or address.
* **Token details**: Users can click on each token to view detailed information.
- The details of the token on SEI blockchain.
# Collection details
Source: https://docs.seitrace.com/assets/non-fungible-tokens/collection-details
The Collection details page provides comprehensive information about a specific NFT collection on Sei Network. This page supports both collections with and without pointers.
## **Basic information**
The Collection details page includes the following basic information about the NFT collection:
* **Total items**: The total number of NFTs within the collection.
* **Holders**: The number of unique owners of NFTs within the collection.
* **Transfers**: The total number of transfers involving NFTs in the collection.
* **Contract information**: Details about the collection contract, indicating whether it is an original or a pointer.
* **Original contract address**: The address of the original contract.
* **Pointer contract address**: The address of the pointer contract, if applicable.
## **Inventory**
Display the inventory of NFTs within the collection. For collections with pointers, show the associated address of the owner alongside each NFT and for collection without pointers, do not show the associated address.
## **NFT Transfers**
Display a list of recent NFT transfers within the collection, including:
* Transaction hash & its associated trx hash (if having) & timestamp
* Type & method of transaction
* From
* To
* Token ID
## **Token Holders**
The collection holders section displays a list of addresses holding NFTs in a specific collection on the SEI blockchain. The display adapts depending on whether the collection uses pointers or not.
* **Without pointer**: If the collection does not include a pointer, it shows only one type of address (either EVM or Native Sei).
* **With pointer**: If the collection includes a pointer, it shows both the EVM and Native Sei addresses of the owner.
## **Contract information**
Provide detailed information about the token contract.
The NFT details page provides comprehensive information about a specific NFT on Sei Network.
# Non Fungible Tokens (NFTs)
Source: https://docs.seitrace.com/assets/non-fungible-tokens/collections
Sei Network supports various standards for non-fungible tokens (NFTs) across both EVM and Native Sei environments.
## **Supported Token Standards**
* **EVM**:
* ERC-721
* ERC-1155
* **Native SEI**:
* CW-721
## Collections
The collections list page provides an overview of all non-fungible token (NFT) collections on Sei Network, including those on both EVM and Native Sei. This page allows users to explore and view details about each NFT collection.
### **Key features**
**Collection List**:
* Display a comprehensive list of NFT collections available on the Sei Network.
* Each row in the collection list includes the following information: Collection name & its address, pointer, token type, items, and number of holders.
### **Filter and search:**
* Users can filter collections by EVM/Native Sei & filter by type of collection and search for specific collections by name or address.
### **Collection Details:**
* Users can click on each collection to view detailed information.
The Collection details page provides comprehensive information about a specific NFT collection on Sei Network.
# NFT details
Source: https://docs.seitrace.com/assets/non-fungible-tokens/nft-details
The NFT details page provides comprehensive information about a specific NFT on Sei Network. This page includes detailed data about the NFT's contract, ownership, properties, and activities.
## **Overview**
The overview section displays essential information about the NFT:
* **Contract information**:
* **Original contract address**: The address of the original contract.
* **Pointer contract address**: The address of the pointer contract, if applicable.
* **Token ID**: The unique identifier of the NFT.
## **Owner Information**
* **Owner address**: The address of the current owner of the NFT.
* **Associated address**: If the NFT is part of a collection that includes pointers, display both the EVM and Native Sei addresses of the owner.
## **Properties & description:**
* Key attributes and traits of the NFT.
* A brief description of the NFT.
## **Item activities**
The item activities tab displays a history of activities related to the NFT. If the NFT is a pointer, it shows activities from both the original and pointer contracts.
* **Trx hash & it's associated trx hash (if having) & included the timestamp**
* **Activity type**: The type of activity (e.g., transfer, sale).
* **From address**: The address that initiated the activity.
* **To address**: The address that received the activity.
## **Metadata**
The Metadata tab provides detailed metadata for the NFT, including:
* **Metadata attributes**: Key-value pairs detailing specific properties of the NFT.
* **Metadata URL**: The URL where the metadata is stored (if applicable).
# Account details
Source: https://docs.seitrace.com/browsing-the-site/account-details
On the SEI blockchain, accounts have two wallet addresses: an EVM-compatible address (0x...) and a COSMOS-compatible address (sei...). These addresses correspond to the same account but operate on different layers of the SEI ecosystem.
## **Address association**
* **Separate accounts**: When the EVM and Native SEI (COSMOS) addresses are not associated, they are displayed as separate accounts.
* [**Associated accounts**](/evm-wasm/associated-accounts): Once the addresses are associated, they are displayed synchronously on a single interface. This means that regardless of which address you are viewing, you can see the transaction history, token holdings, and SEI balance for both addresses. The SEI balance is synchronized across both addresses.
### **Account details display**
The account details page includes the following information:
* **SEI balance**:
* Before association: Each address (0x... and sei...) displays its own separate SEI balance.
* After association: The SEI balance is synchronized and calculated as the combined total of both addresses at the time of association. This synchronized balance is displayed for both addresses.
* **Token holdings**: A list of tokens held by the account, including balances and details for both EVM and COSMOS tokens.
* **Transaction history**: A comprehensive history of all transactions involving the account, including both EVM and COSMOS transactions.
* **Gas used**: The total amount of gas used by the account in its transactions.
* **Internal transactions**: Transfers of SEI carried out through smart contracts, providing deeper insights into the account's activity.
By presenting this information in a unified view, users can easily manage and monitor their accounts regardless of the underlying address type, ensuring a seamless and integrated experience on the SEI blockchain.
# Blocks
Source: https://docs.seitrace.com/browsing-the-site/blocks
## **Blocks list**
The Blocks page provides a comprehensive view of all blocks in the SEI ecosystem, offering essential statistics and detailed information about each block.
### **Basic stats**
Display key statistics about the blocks:
* **Block height**: The current height of the blockchain, indicating the total number of blocks.
* **Block time**: The average time taken to produce a new block.
### **Blocks list**
Each row of block includes the following data:
* **Block number & time**: The unique identifier of the block and the timestamp when it was created.
* **Validator**: The validator that verified and added the block to the blockchain.
* **Txn count**: The number of transactions included in the block.
* **Gas used**: The total amount of gas used by the transactions in the block.
* **Reward SEI**: The reward in SEI given to the validator for producing the block.
By organizing this information clearly, users can easily navigate and understand the performance and activity of Sei Network through its blocks.
## **Block details**
Seitrace provides basic data about each block:
* \*\*Details tab: \*\*display the following detailed fields: Block height, Size, Timestamp, Transactions (count), Validated by, Gas usage, Gas limit, Base fee per gas, Block hash and parent hash. Each field is defined by the included tooltip.
* **Transactions tab**: displays a list of transactions included in the block both EVM & Native Sei.
By organizing this information clearly, users can easily navigate and understand the performance and activity of Sei Network through its blocks and the transactions they contain.
# Code ID
Source: https://docs.seitrace.com/browsing-the-site/code-id
Doc coming soon
# Contract details
Source: https://docs.seitrace.com/browsing-the-site/contract-details
The contract details page provides comprehensive information about a contract on the SEI blockchain. Contracts are treated similarly to addresses/accounts but include additional contract-specific details.
## Common features with [**addresses (accounts)**](/browsing-the-site/account-details)
Contracts share several features with regular addresses, such as:
* **Transaction history**: Displaying all transactions involving the contract.
* **Token holdings**: Listing tokens held by the contract.
* **Balance SEI**: Showing the SEI balance of the contract.
* **Internal txns**: Displaying internal transactions, which are SEI transfers carried out via smart contracts.
* **Associated account**: Supporting associated accounts, allowing users to view synchronized information across both EVM and COSMOS addresses. Learn more here.
## **Contract-specific features**
In addition to the common features, the contract details page includes:
* \*\*More information: \*\*Token name, Contract name, Contract creator, Contract type, Implementation
* **Logs tab**: Displaying logs generated by the contract.
* **Detailed contract information**: Providing in-depth details about the contract, such as its creation code, deployed bytecode, verification status and interaction between wallet and contract.
## **EVM contract verification status**
EVM contracts can have three verification statuses:
1. **Unverified**:
* **Details**: Users can see the Contract Creation Code and Deployed ByteCode.
* **Interaction**: Users need to verify and publish the contract to interact with it.
2. **Partial Match (Partially Verified)**:
* **Details**: Users can see partially matched source code, ABI (Application Binary Interface), and other contract details. This indicates that some parts of the contract match the source code provided, but not entirely. User can continue to [Verify & publish](/browsing-the-site/verified-contracts) for exact match
* **Interaction**: Users can interact with the contract, but some functionality may be limited due to partial verification.
3. **Exact Match (Fully Verified)**:
* **Details**: Users can see the fully verified source code, ABI, and complete contract details. This indicates that the contract's source code exactly matches the deployed bytecode.
* **Interaction**: Users can fully interact with the contract, utilizing all its functionalities.
## **Native SEI Contracts (COSMOS)**
Currently, contract verification for Native SEI (COSMOS) contracts is not supported.
## **Visual indicators**
* **Verified contracts**: Use an icon with a green checkmark on a green background to indicate a verified contract.
* **Unverified contracts**: Use a gray icon to indicate an unverified contract.
# Homepage
Source: https://docs.seitrace.com/browsing-the-site/homepage
This is the main window when users interact with Seitrace for the first time.
On the homepage, users are greeted with a comprehensive overview of the Sei ecosystem, featuring:
* **Basic stats:** Instantly view key statistics such as total transactions, blocks, TPS, average block time, total stake, and active accounts on the Sei Network.
* **Price information:** Stay updated with the latest SEI price, real-time market cap, and daily transaction volume, all visualized with dynamic charts.
* **Global search toolbar:** Access a powerful search tool for quickly finding addresses, transaction hashes, tokens, NFT collections, and more across the network.
* **Top earnings:** See top-earning pools by APR and TVL, helping users discover the most rewarding DeFi opportunities on Sei.
* **Latest blocks:** Recent blocks for both EVM and Native Sei. Users can view[ all the blocks ](/browsing-the-site/blocks)displayed on the Sei Network by clicking on the "View All" button.
* **Latest transactions:** Recent transactions for both EVM and Native Sei. Users can [view all the transactions ](/browsing-the-site/transactions)displayed on the Sei Network by clicking on the "View All" button.
* **Airdrops:** Access the latest airdrop campaigns and opportunities.
* **Validators:** Get an overview of leading validators, their voting power, and staking APR, with options to view the full validator list.
* **SEI Tools:** Quickly access essential tools, including token transfers, multisender, address book, SEI faucets, and profile management for seamless navigation and interaction within the Sei ecosystem.
This unified homepage ensures that users can monitor network health, market trends, and personal opportunities with ease—all from a single, intuitive homepage.
# IBC Relayers
Source: https://docs.seitrace.com/browsing-the-site/ibc-relayers
## IBC Relayers
List of IBC Relayers interacting with SEI Blockchain.
### **Statistics**
* **Connected Chains**: The total number of chains connected to the SEI blockchain via IBC.
* **Total Channels**: The number of channels that SEI blockchain connected to other chains via IBC.
* **Total Send**: The total number of transactions executed to send tokens via IBC relayers.
* **Total Receive**: The total number of transactions executed to receive tokens from IBC relayers.
### **All connected chains**
This section lists all chains connected to the SEI blockchain within the Cosmos ecosystem. Each entry includes:
* **Chain**: The name and identifier of the chain.
* **Total**: The number of transactions executed via the relayer between the SEI blockchain and the chain, including successful, failed, and pending transactions.
* **Receive**: The number of asset transactions received via the relayer, including successful, failed, and pending.
* **Send**: The number of asset transactions sent via the relayer, including successful, failed, and pending.
* \*\*Status: \*\*The current status of the connection between the SEI blockchain and the chain.
* **Channels**: The number of active channels versus the total connected channels between the SEI blockchain and the chain.
Users can filter by status or search by chain name or chain ID.
Clicking on a chain provides detailed information about the relayer.
## **Relayer details**
The Relayer Details provides information about the list of channels and their status.
Each entry includes:
* **Channel (Sei)**: The channel from the Sei blockchain.
* **Channel (Connected Chain)**: The channel from the connected blockchain.
* **Status**: The current status of the channel connection.
* **Operating Since**: The date the channel started operating.
* **Total**: The number of transactions executed via the channel, including successful, failed, and pending.
* **Received**: The number of asset transactions received via the channel, including successful, failed, and pending.
* **Sent**: The number of asset transactions sent via the channel, including successful, failed, and pending.
## **Channel details**
### **Overview Information**
* **Connected Channel**: Displays the name and status of the channel connection.
* **Counterparty**: The channel from the connected blockchain.
* **Operating Since**: The date the channel started operating.
* **Total Transactions**: The number of transactions executed via the channel, including successful, failed, and pending.
* **Client ID**: The identifier Tendermint associated with the channel.
### **Transfer assets Tab**
This tab displays assets transferred through the channel:
* **IBC Sending Assets**: Lists assets, quantities, and the number of transfers from Sei to the connected chain.
* **IBC Receiving Assets**: Lists assets, quantities, and the number of transfers received from the connected chain to Sei.
### **Transactions Tab**
Displays a list of transactions transferring in and out of the Sei blockchain via the channel.
# Proposals
Source: https://docs.seitrace.com/browsing-the-site/proposals
The navigation field in docs.json defines the pages that go in the navigation menu
## **Proposal list page**
### **Statistics**
* **Total Proposals**: Displays the total number of proposals submitted on the SEI blockchain.
* **Active Proposals**: Shows the number of proposals currently open for voting.
* **Passed**: Indicates the number of proposals that have been approved.
* **Rejected & Failed**: Lists the number of proposals that were either rejected or failed.
### **Active Proposals**
This section lists all proposals currently open for voting, allowing users to participate in the decision-making process.
### **All proposals**
This section includes all proposals from the SEI blockchain, their status includes:
* **In Deposit Period**: Proposals awaiting sufficient deposits.
* **In Voting Period**: Active proposals available for voting.
* **Passed**: Proposals that have been approved.
* **Rejected**: Proposals that have been turned down.
* **Failed**: Proposals that did not pass.
* **Not Enough Deposit**: Proposals lacking the required deposit.
Each proposal entry includes:
* **ID**: The unique identifier of the proposal.
* **Title & Type**: The name and type of the proposal.
* **Status**: The current state of the proposal.
* **Voting Ends**: The deadline for voting.
* **Proposed By**: The address of the proposer.
Users can click "View" to see more details of each proposal.
User can also filter by status or search by proposal ID or proposal title.
## **Proposal details**
### **Overview Information**
* **Proposal ID**: The unique identifier of the proposal.
* **Proposal Name**: The name of the proposal.
* **Status**: The current state of the proposal.
* **Most Vote On**: Shows the option with the most votes: Yes, No, Veto, Abstain.
* **Turnout/Quorum**: The participation rate in the voting process.
* **Type**: The type of proposal.
* **Create Tx**: The transaction hash where the proposal was created.
* Vote options and their voted:
* Yes: Agree with the proposal.
* No: Disagree with the proposal.
* No, with Veto: Strongly disagree with the proposal and request the deposit to be burned.
* Abstain: Choose not to vote either for or against the proposal but still participate in the governance process.
### **Details Tab**
Displays detailed information about the proposal: **Title**, Type, Description, Details, Voting Start, Voting End, Submit Time, Deposit End, Total Deposit
### **Votes Tab**
* \*\*Recent Votes: \*\*Lists recent votes from users and validators. Includes each address's vote choice and transaction hash for details.
* \*\*Validator Votes: \*\*Displays all validators and their votes. Shows each validator's vote choice and transaction hash for further details.
### **Depositors tab**
Shows a list of depositors and their deposit amounts. Includes transaction hashes for each deposit, allowing for detailed exploration.
# Search bar
Source: https://docs.seitrace.com/browsing-the-site/search-bar
The Search bar allows you to search for tokens, addresses, blocks, and transaction trackings in a clean and easy-to-follow manner.
* **Search tokens**:
* Users can type the token name, collection name, or token address.
* Support to display the verified token during searches.
* **Search addresses**:
* Users can type the name of a contract, account label, or the name of a token related to the contract.
* Enter the correct address
* Support pointer contract search
* **Search blocks**: Users can search by block number.
* **Search transactions**: Users can search by transaction hash.
* **Support recent searches**: Quickly access your recent searches for convenience.
# Top accounts
Source: https://docs.seitrace.com/browsing-the-site/top-accounts
The Top Accounts page highlights the accounts with the highest SEI balance, providing insights into the wealth distribution within the SEI ecosystem.
## Account list
Provide a detailed list of the top accounts sorted by SEI balance. Each entry should include:
* **Rank**: The rank of the account based on SEI balance.
* **EVM address**: The account's EVM address.
* **Native address**: The account's Native SEI address.
* **Public tag**: A public label of the account (if available).
* **Total balance SEI**: The current SEI balance held by the account.
* **Percentage**: The percentage of the total SEI supply held by the account.
* **Txn count**: The total number of transactions conducted by the account.
By organizing this information clearly, users can easily navigate and understand the distribution of SEI balances across the top accounts, as well as identify accounts with both EVM and native addresses, ensuring data synchronization is evident.
# Transactions
Source: https://docs.seitrace.com/browsing-the-site/transactions
## Transaction list
### **Basic Stats**
Display essential statistics about transactions:
* **Completed transactions**: The number of transactions with success status.
* **Total transactions**: The total number of transactions including: pending, dropped, replaced, failed and success status.
### **Transaction list**
Provide a comprehensive list of transactions, covering both EVM and Native SEI. Each transaction entry should include:
* **Transaction hash**: The unique identifier of the transaction.
* [**Associated transaction hash**](/evm-wasm/associated-transactions): The hash of the associated transaction, if applicable.
* **Status**: The current status of the transaction (e.g., pending, success, failed).
* **Type & method**: The type of the transaction (e.g., coin transfer, token transfer, contract call, contract creation, token burning, token creation, token minting, transaction) and method of transaction.
* **Block**: The block number in which the transaction is included.
* **From/To**: The sender and recipient addresses of the transaction.
* **SEI Value**: The value transferred in SEI.
* **Fee SEI**: The transaction fee in SEI.
### **Tabs**
* **Tab EVM**: Displays transactions on the EVM.
* **Tab Native SEI**: Displays transactions on Native SEI.
By organizing transactions into these tabs and providing detailed information, users can easily navigate and understand transaction activities across both environments.
## **Transaction details**
### **EVM transaction**
### **On EVM transactions, show:**
* **Details tab:** display the following detailed fields: [Associated trx hash](/evm-wasm/associated-transactions), Transaction hash, Status and method, Block, Timestamp, Transaction action, From, To/Interacted with contract, Token transferred, Token burnt, Token minted, Value, Transaction fee, Gas price, Gas usage & limit by txn, Gas fees, Burnt fee, Raw input and Decoded input data. Each field is defined by the included tooltip.
* **Token transfers tab**: display list of token transfers transactions
* **Internal txns tab**: Show the transfers of SEI carried out through a smart contract as an intermediary.
* **Logs tab**: Display the logs exposed from the blockchain, detailing events and actions taken during the transaction.
* **State tab**: Display the changes in balance resulting from the transaction.
By organizing these details into clear categories, users can easily access and understand the comprehensive information related to each EVM transaction.
### **Native SEI transaction**
### **On Native SEI transactions, show:**
* **Details tab:** display the following detailed fields: [Associated trx hash](/evm-wasm/associated-transactions), Transaction hash, Status and method, Block, Timestamp, Memo, Messages & their details, Signed by, Value, Transaction fee, Gas price, Gas usage & limit by txn. Each field is defined by the included tooltip.
* **Token transfers tab**: display list of token transfers transactions
* **Logs tab**: Display the logs exposed from the blockchain, detailing events and actions taken during the transaction.
By organizing these details into clear categories, users can easily access and understand the comprehensive information related to each SEI transaction.
# Validators
Source: https://docs.seitrace.com/browsing-the-site/validators
## **Validator list**
The Validators page provides a comprehensive view of the validators in the SEI ecosystem, offering essential statistics and detailed information about each validator.
### **Basic stats**
Display key statistics about the validators:
* **Total validators**: The total number of validators in the network.
* **Active validators**: The number of validators currently active and participating in consensus.
* **Inactive validators**: The number of validators that are currently inactive.
* **Jailed validators**: The number of validators that have been jailed due to misbehavior or failing to meet the network requirements.
### **Validator list**
Provide a searchable and filterable list of validators with the following features:
* **Filter by status**: Users can filter the list to show only active, inactive, or jailed validators.
* **Search by validator name or address**: Users can search for a validator by its name or operator address.
Each row of validator includes the following data:
* **Validator name & operator address**: The name of the validator and its operator address.
* **Voting power**: The voting power of the validator, indicating its influence in the network.
* **Commission**: The commission rate charged by the validator for its services.
* **Participation**: The level of participation by the validator in the consensus process.
* **Uptime**: The uptime percentage, showing how reliably the validator has been online.
By organizing this information clearly, users can easily navigate and understand the performance and status of validators within the Sei Network.
## **Validator details**
V1.0.0
In this version, Seitrace provides basic data about each validator, with more detailed information supported in future updates.
* **Validator Name**
* **Voting power in SEI & percentage**: The amount of SEI and the percentage of total voting power.
* **Status**: The current status (active, inactive, jailed).
* **Delegators**: The number of delegators supporting the validator.
* **Commission**: The commission rate.
* **Max Rate**: The maximum commission rate.
* **Max Change Rate**: The maximum rate at which the commission can change.
* **Updated**: The last time the validator's information was updated.
* **Addresses**: account address, operator address, consensus address, and hex address.
By organizing this information clearly, users can easily navigate and understand the performance and status of validators within the Sei Network. Detailed data will be expanded in future versions to provide even more insights into each validator's operations and performance.
# Verified contracts
Source: https://docs.seitrace.com/browsing-the-site/verified-contracts
In version 1.0.0, we support displaying verified contracts for EVM only. Seitrace will support Native SEI contract in upcoming version.
## **Basic stats**
Display basic statistics about contracts:
* **Total contracts (EVM)**: The total number of contracts on EVM.
* **Verified contracts (EVM)**: The number of verified contracts on EVM.
## **Latest verified contracts**
Display a list of the latest verified contracts. Basic information includes:
* **Contract name & address**: The name of the contract and its address.
* **Balance SEI**: The SEI balance of the contract (supported for associated).
* **Txs**: The number of transactions involving the contract.
* **Compiler/Version**: The compiler and version used to create the contract.
* **Verification time (Verified)**: The time when the contract was verified.
## **Filtering and Search**
Users can:
* **Filter by compiler**: Filter the list of contracts by compiler.
* **Search by contract name or its address**: Search for contracts by their name or address.
# Product updates
Source: https://docs.seitrace.com/changelog/product-updates
Keep track of changes and updates
## New tools and new LP Staking
### **🚀 Seitools — Do More, Faster**
* 🪙 [Create Token](https://seitrace.com/tool/create-token): Launch new tokens with a guided setup.
* 📌 [Deploy Pointer](https://seitrace.com/tool/deploy-pointer): Create and manage token pointers for seamless tracking.
* 🔁 [Swap Token](https://brrr.fun/swap): Swap assets with a smoother, more reliable flow.
### 💰 Earnings — New LP Staking
🟡 Kura LP Staking: Stake Kura LP tokens and monitor rewards directly in Earnings.
### 🖼️ NFTs — Clearer Market Signals
* 📉 Floor Price % Change: New column showing percentage changes in floor price.
* 🔎 Sorting & Filtering: Sort/filter by floor, % change, volume, and more.
### ⚙️ Seitrace MCP
Bring Seitrace data to [AI via Model Context Protocol](https://seitrace.com/mcp).
### 📊 Performance & Reliability
* ⚡ Faster load times and smoother navigation.
* 🛠️ Fixed minor bugs
**Try SeiTrace 1.14.0 today and explore these upgrades across Seitools, Earnings, MCP, and NFTs!**
## Utility tools and expanded data
This update brings new utility fees to support our tools, along with a significant expansion of data for NFTs and projects.
* **Send Tokens:** The token sending feature now has a fee of 0.1 SEI per token.
* **Multisender:** The multisender tool now charges a fee of 0.05 SEI per address.
* **NFT Data:** We added a **Floor Price** for NFT collections and **Price** for individual NFT IDs, giving you more market insights.
* **Marketplace List:** Find a new, centralized list of all supported marketplaces.
* **API Button:** An **API** button is now available on relevant pages for quick access to our documentation.
* **Project Submission:** You can now include **smart contracts** when submitting a new project.
## NFT Analytics & Account Filters
New data for NFTs and powerful tools to organize and track on-chain accounts.
* **NFT Analytics:** Now featuring comprehensive NFT market data, including volume, activities and marketplaces.
* **Account Filters:** Filter accounts by category for easier tracking and analysis.
## Streamlined Exploration & Integration
This update introduces new features to help you personalize your on-chain data and integrate more deeply with our platform.
* **Name Tagging:** Easily add or update custom names for contracts and accounts for a personalized view.
* **Project Directory:** A comprehensive directory of Sei ecosystem projects, with the option to submit and update project information.
* **API Docs**: Access the API documentation quickly and conveniently from every page.
## Deeper Validator Info, New Lending & Enhanced Token Submission
We've rolled out exciting enhancements to Seitrace:
* **Validators:** Access more detailed validator profiles, now including comprehensive delegation and delegator information.
* **Earning:** Explore new "Lending" opportunities (starting with Takara). Earning pools now feature richer details, sharing options, and earning calculators.
* **Token Info:** Submitting token information is now more comprehensive. You can now **add new fields "Symbol" and "Decimals"** to ensure precise token display on Seitrace.
## New Homepage, Airdrop Hub, Earning & Faucets!
**New Homepage**
* We've redesigned the homepage for a cleaner, faster, and more informative user experience.
* Try it: [https://seitrace.com/?chain=pacific-1](https://seitrace.com/?chain=pacific-1)
**Earning**
* Discover staking pools and yield aggregator vaults across SEI — all earning opportunities, centralized.
* Try it: [https://seitrace.com/earning?chain=pacific-1](https://seitrace.com/earning?chain=pacific-1)
**Airdrop Hub**
* Explore all active and historical airdrop programs on the SEI blockchain in one place.
* Try it: [https://seitrace.com/airdrop?chain=pacific-1](https://seitrace.com/airdrop?chain=pacific-1)
**Sei Faucets**
* Now supporting both SEI Testnet and Devnet — easily request SEI tokens for development and testing.
* Try it: [https://seitrace.com/tool/faucet?chain=pacific-1](https://seitrace.com/tool/faucet?chain=pacific-1)
\-----------\
**Improvements & Fixes**
* Enhanced overall site performance and loading speed
* Fixed several bugs for a more stable experience
## Leveling up your Sei experience with powerful tools, better security, and smarter insights.
We've rolled out exciting enhancements to Seitrace:
* **Associate Account (Seitools)** [Link your EVM & Native Sei wallets](https://seitrace.com/tool/associate) for seamless portfolio management and cross-chain activity tracking — one view, total control.
* **Submit Token Info:** Project teams can now directly [submit and update token details](https://seitrace.com/submit/token) on Seitrace — fully supports all token types within the Sei ecosystem.
* **Token Security Score** (Powered by Webacy): Stay safe while exploring Sei. Instantly view [token security ratings](https://seitrace.com/token/0xE30feDd158A2e3b13e9badaeABaFc5516e95e8C7) to help protect yourself from risks and bad actors.
* **Earning Section:** Discover all [earning opportunities](https://seitrace.com/earning) across the Sei ecosystem — staking pools, vaults, rewards programs, and more. All in one place.
* **Live Token Price Charts**: Track token performance with [real-time charts ](https://seitrace.com/token/0xE30feDd158A2e3b13e9badaeABaFc5516e95e8C7)powered by on-chain data. Stay informed with accurate price movements (ERC-20 tokens supported).
# Airdrop
Source: https://docs.seitrace.com/earning/airdrop
Doc coming soon
# Earnings
Source: https://docs.seitrace.com/earning/earnings
Doc coming soon
# Listing new earnings
Source: https://docs.seitrace.com/earning/listing-new-earnings
Seitrace Yield Provider API Integration Documentation
**Version:** 1.0
**Date:** 2025-04-22
## **Objective**
To allow Seitrace to accurately display yield-generating opportunities (like staking pools, liquidity pools, vaults, lending markets, etc.) offered by your platform on the Sei blockchain. This requires Providers to expose a standardized API endpoint returning data about their available pools/opportunities.
## **Audience**
This document is intended for the technical teams of Yield Providers integrating with Seitrace.
## **Integration Overview**
Integrating with Seitrace involves two primary components:
1. **A Dynamic API Endpoint:** An HTTP GET endpoint that Seitrace will call periodically to retrieve up-to-date information on your platform's yield pools and opportunities.
2. **Static Provider Information:** A set of descriptive details about your platform provided separately during the onboarding process.
Let's detail each component.
***
## **1. Dynamic Pool Data API (Required)**
The base URL for all API requests is: `https://example-library-api.com`
Each Provider must supply Seitrace with a stable HTTP API endpoint URL.
* **Method:** `GET`
* **URL Structure:** This will be specific to each Provider (e.g., `https://api.yourdomain.com/seitrace/pools`). Please provide the exact URL to the Seitrace team during onboarding.
* **Authentication:** Currently, no specific authentication headers are required. The endpoint should be publicly accessible or use standard mechanisms communicated during onboarding if necessary.
* **Request Headers:** Seitrace will typically include standard headers like `Accept: application/json`.
* **Request Parameters:** No specific query parameters are required by Seitrace for this endpoint at this time.
The API endpoint **MUST** return a JSON object adhering to the structure defined below.
* **Success Status Code:** `200 OK`
* **Content-Type:** `application/json`
### **1.1. Overall Response Structure (**`Response`**)**
The top-level JSON object must contain a single key, `data`, which holds an array of `IPoolInfo` objects.
```javascript
export type Response = {
data: IPoolInfo[]; // Array containing details for each pool/vault/opportunity
}
```
### **1.2. Pool Information (**`IPoolInfo`**)**
Each object within the `data` array represents a single yield opportunity and must conform to the `IPoolInfo` structure.
```javascript
type IPoolInfo = {
pool_type: PoolType; // Specify pool type
pool_name: string; // Clear, human-readable name of the pool/vault/strategy (e.g., "SEI/USDC", "wSEI").
pool_url: string; // Direct deep-link URL to the specific pool/vault page on the Provider's website.
pool_address: string | null; // Contract address of the pool/vault on the Sei blockchain. Provide `null` if not applicable (e.g., for delegated staking).
pool_image: string | null; // URL to an image/icon representing the pool (e.g., pair icons). `null` if not available.
total_apr: number; // The overall total Annual Percentage Rate (APR) for the pool, calculated by summing all base and incentive APRs. **Represent as a percentage value (e.g., 15.5 for 15.5%).**
total_apy: number | null; // The overall total Annual Percentage Yield (APY) if compounding is involved (auto-compounding or manual). **Represent as a percentage value (e.g., 16.7 for 16.7%).** Provide `null` if APY is not applicable or cannot be calculated.
deposit_tokens: IDepositToken[]; // An array detailing the token(s) users need to deposit into this pool. See section 2.3.
is_auto_compound: boolean | null; // Set to `true` if the rewards are automatically compounded back into the principal. Set to `false` if compounding is manual or not applicable. Provide `null` if unsure or not applicable.
aprs: IAPR[]; // An array detailing the breakdown of different APR sources (base vs incentives). See section 2.4.
fee: number | null; // Any performance fee, withdrawal fee, or deposit fee associated with the pool. **Represent as a percentage value (e.g., 5 for 5%).** Provide `null` if no fees apply. Clarify fee type with Seitrace team if ambiguous.
tvl: number; // Total Value Locked in the pool, denominated in **USD**.
lock_period: number | null; // If applicable, the lock-up period for staking/deposits in SECONDS (e.g., 86400 for a 1-day lock). Leave `null` if not applicable.
}
```
### **1.3. Deposit Token Information (**`IDepositToken`**)**
Details about the tokens required for depositing into the pool.
```javascript
type IDepositToken = {
address: string; // Contract address of the deposit token on Sei.
deposited_amount: number | null; // Total amount of THIS token currently deposited in the pool across all users. (e.g., 12064.41). Provide `null` if not available.
name: string | null; // Human-readable name (e.g., "Wrapped Ether"). Provide `null` if not readily available*.
symbol: string | null; // Ticker symbol (e.g., "WETH"). Provide `null` if not readily available*.
icon_url: string | null; // URL to the token's icon. Provide `null` if not available*.
decimals: number | null; // The token's decimal precision (e.g., 18). Crucial for correct value interpretation. Provide `null` if not readily available*.
coingecko_id: string | null; // The CoinGecko identifier for the token (e.g., "wrapped-ether"). Helps Seitrace fetch market data. Provide `null` if not available*.
min_deposit: number | null; // Minimum amount of this token required for a single deposit transaction. Provide `null` if no minimum.
max_deposit: number | null; // Maximum amount of this token allowed for a single deposit transaction. Provide `null` if no maximum.
};
```
### **1.4. Reward Breakdown (**`IRewardData`**)**
Details the components contributing to the total APR.
```javascript
enum RewardType {
BASE = 'base', // Yield generated directly from the pool's core activity (e.g., trading fees for LPs, protocal reward, yield bearing tokens).
INCENTIVE = 'incentive', // Additional rewards provided, often in a different token, to incentivize participation.
}
type IRewardData = {
reward_token: IRewardToken; // Details of the token being paid out as reward for this specific APR component. See section 2.5.
type: RewardType; // Must be either 'base' or 'incentive'.
apr: number | null; // The APR for this specific component. **Represent as a percentage value (e.g., 10.2 for 10.2%).** Provide `null` only if absolutely unavailable.
apy: number | null; // The APY for this specific component, *if applicable and calculable separately*. Often `null` as total APY is usually calculated at the pool level. **Represent as a percentage value.**
};
```
### **1.5. Reward Token Information (**`IRewardToken`**)**
Details about the token being distributed as rewards for a specific APR component.
```javascript
type IRewardToken = {
address: string; // Contract address of the reward token on Sei.
name: string | null; // Human-readable name (e.g., "Wrapped SEI"). Provide `null` if not readily available*.
symbol: string | null; // Ticker symbol (e.g., "WSEI"). Provide `null` if not readily available*.
icon_url: string | null; // URL to the token's icon. Provide `null` if not available*.
decimals: number | null; // The token's decimal precision. Provide `null` if not readily available*.
coingecko_id: string | null; // The CoinGecko identifier. Provide `null` if not available*.
};
```
* ***Note on Token Info (***`name`**\_, \_**`symbol`**\_, \_**`icon_url`**\_, \_**`decimals`**\_, \_**`coingecko_id`***):*** While Seitrace *may* attempt to look up missing token information using the provided `address`, it is **strongly recommended** that Providers include this data directly in the API response for accuracy, performance, and correct display on Seitrace. Please provide `null` only if the information is genuinely unavailable from your systems.
### **1.6. Pool Type (**`PoolType`**)**
```javascript
export enum PoolType {
LP = 'LP', // Liquidity Pool Provision
DELEGATED = 'DELEGATED', // Native Staking Delegation
LIQUID = 'LIQUID', // Liquid Staking Tokens
YIELD_AGGREGATOR = 'YIELD_AGGREGATOR', // Vaults, Auto-compounders
LENDING = 'LENDING', // Money Markets
}
```
### **1.7. Example Response**
```json
{
"data": [
{
"pool_type": "YIELD_AGGREGATOR",
"pool_name": "WETH Vault",
"pool_url": "",
"pool_address": "0x0AEfC6F2E9a866ddB4813Cb1E897a2E9e26a1E53",
"pool_image": "",
"total_apr": 6.268655367391925,
"total_apy": null,
"is_auto_compound": false,
"fee": 5,
"tvl": 1579.50,
"lock_period": null,
"deposit_tokens": [
{
"address": "0x160345fC359604fC6e70E3c5fAcbdE5F7A9342d8",
"deposited_amount": 12064.4126408933883,
"name": "Wrapped Ether",
"symbol": "WETH",
"icon_url": "",
"decimals": 18,
"coingecko_id": "wrapped-ether",
"min_deposit": 0.01,
"max_deposit": null
}
],
"aprs": [
{
"type": "base",
"apr": 6.0,
"apy": null,
"reward_token": {
"address": "0x160345fC359604fC6e70E3c5fAcbdE5F7A9342d8",
"name": "Wrapped Ether",
"symbol": "WETH",
"icon_url": "",
"decimals": 18,
"coingecko_id": "wrapped-ether"
}
},
{
"type": "incentive",
"apr": 0.268655367391925,
"apy": null,
"reward_token": {
"address": "0xE30feDd158A2e3b13e9badaeABaFc5516e95e8C7",
"name": "Wrapped SEI",
"symbol": "WSEI",
"icon_url": "",
"decimals": 18,
"coingecko_id": "wrapped-sei"
}
}
]
}
]
}
```
***
## **2. Provider Information (Separate Submission)**
In addition to this dynamic pool data API, Seitrace requires some static information about your platform (the Provider). This information is typically collected once during onboarding and updated manually as needed. Please be prepared to provide the following details to the Seitrace team:
### **2.1. Provider Information (**`ProviderInfo`**)**
```javascript
type ProviderInfo = {
provider_name: string; // Your official brand name (e.g., "Pit Finance").
provider_home_url: string; // URL of your project's main homepage (e.g., "").
provider_base_url: string; // Base URL used to construct individual pool links if needed (e.g., ""). Often the `pool_url` provided in the API is sufficient.
provider_datasource_endpoint: string; // The functional API endpoint URL you created based on this documentation.
provider_logo: string; // URL to your project's official logo (preferably SVG or high-res PNG).
provider_description: string | null; // A brief description of your platform/service.
how_to_stake: string | null; // Simple, newline-separated (\\n) steps on how users typically stake/deposit on your platform.
how_to_unstake: string | null; // Simple, newline-separated (\\n) steps on how users typically unstake/withdraw on your platform.
}
```
### **2.2. Example Response**
```javascript
{
"provider_name": "Pit Finance",
"provider_home_url": "",
"provider_base_url": "",
"provider_datasource_endpoint": "",
"provider_logo": "",
"provider_description": null,
"how_to_stake": "Connect your wallet\\nSelect a vault\\nEnter the deposit amount\\nApprove the transaction\\nConfirm the deposit\\nMonitor your position",
"how_to_unstake": "Connect your wallet\\nNavigate to your vault position\\nSelect the amount to unstake\\nConfirm the withdrawal\\nReceive your assets"
}
```
***
## **Additional Guidelines**
* **Data Freshness:** The data provided via the API should be kept reasonably up-to-date. Aim for updates at least every **5-15 minutes** if possible, especially for TVL and APR/APY figures which can change frequently. If data is less dynamic (e.g., delegated staking APRs), less frequent updates (e.g., hourly) may suffice. Please communicate your expected update frequency to Seitrace.
* **Accuracy:** Ensure the APR, APY, TVL, and fee data accurately reflects the current state of the pool on your platform.
* **Completeness:** Provide values for all fields where possible. Use `null` only when data is truly unavailable or not applicable. Accurate `pool_url`, `pool_address`, `deposit_tokens.address`, `reward_token.address`, `total_apr`, and `tvl` are particularly important.
* **Units:** Remember to use **percentage values** for `total_apr`, `total_apy`, `aprs.apr`, `aprs.apy`, and `fee`. Use **USD** for `tvl`.
* **Error Handling:** In case of internal errors preventing data retrieval, the endpoint should return an appropriate HTTP error code (e.g., `500 Internal Server Error`) with a minimal JSON error message if possible, e.g., `{"error": "Failed to retrieve pool data"}`.
#### **Support**
If you have questions or require assistance implementing this API, please contact the Seitrace integration team at: [support@seitrace.com](mailto:support@seitrace.com)
# Associated accounts
Source: https://docs.seitrace.com/evm-wasm/associated-accounts
Seitrace recognizes and displays both associated and non-associated accounts
## Overview
On Sei Network, each account has two distinct addresses:
* **EVM Address**: Starts with `0x...`
* **Native Sei Address**: Starts with `sei...`
These addresses represent the same account but exist in different execution environments (EVM and Native SEI). To provide a seamless user experience, Sei blockchain supports associating these two addresses into a single account.
## How association works
**Associated account**: An associated account is one where the EVM and Native Sei addresses have been linked. This linkage occurs automatically when a user performs any transaction from either address. Once associated, the following features come into play:
* **Unified balance**: The SEI balance will be updated regardless of which address (EVM or Native Sei) is used for transactions.
* **Synchronized data**: All data related to transactions, token transfers, and token holdings will be synchronized across both addresses.
## Features on Seitrace
Seitrace recognizes and displays both associated and non-associated accounts, providing comprehensive visibility into account activities. Here’s how it works:
* **Associated accounts**: Seitrace identifies and links the two addresses, displaying them as a single account with merged transaction history, combined balances and token holdings.
* **Non-associated accounts**: For accounts that are not yet associated, Seitrace displays the separate EVM and Native Sei addresses and their respective data.
# Associated transactions
Source: https://docs.seitrace.com/evm-wasm/associated-transactions
On Sei Network, certain transactions specifically establish an association between the signer's Sei address and their EVM address on-chain. Seitrace supports and displays these association transactions to provide transparency and facilitate easier management for users.
# EVM <> Wasm interoperability
Source: https://docs.seitrace.com/evm-wasm/evm-wasm
Seitrace supports seamless EVM and Wasm interoperability.
## EVM \<> Wasm Interoperability
EVM and Cosmos based applications co-exist on Sei, but live in different execution environments. This creates a challenge for users, who use wallets that typically only support a single execution environment. Likewise for devlelopers, existing tooling and libraries can only interact with either EVM or Wasm (Think EthersJS vs CosmJS).
To bridge the gap between EVM and Wasm, Sei has introduced novel interoperability features, allowing for smooth and easy interactions between both environments. These features will enable all contracts deployed to Sei to be accessible by tools and wallets from both environments.
Read more: [https://v2.docs.sei.io/interoperability/overview](https://v2.docs.sei.io/interoperability/overview)
## Supports
On Seitrace, we also supported for:
Link and display pointer and original contracts for both fungible and non-fungible tokens.
Recognize and display both associated and non associated accounts.
Display the associated transaction hash on the details page
# Pointer contracts
Source: https://docs.seitrace.com/evm-wasm/pointer-contracts
Pointer Contracts are a unique feature introduced on Sei, designed to enhance interoperability between EVM and CosmWasm environments. These contracts facilitate the creation of links between tokens across both EVM and CosmWasm. This enables tokens to move smoothly and be used seamlessly in both environments.
Learn more about Pointer Contracts and how to deploy them [here](https://v2.docs.sei.io/interoperability/pointer-contracts).
On Seitrace, we link and display pointer and original contracts for both fungible tokens (CW-20 & ERC-20) and non-fungible tokens (CW-721 & ERC-721).
# Introduction
Source: https://docs.seitrace.com/index
Welcome to the Seitrace documentation page
## What is Seitrace?
> Seitrace is a Block Explorer and Analytics Platform for Sei Network
**Seitrace** is the first explorer to support both the parallelized EVM and Native Sei (on Wasm). As the comprehensive explorer for the Sei Network, Seitrace offers a deep dive into real-time insights of the Sei Network. Track transactions, accounts, contracts, verify contracts, and explore network activity with our intuitive analytics tools.
## Key Features
Interact seamlessly with both EVM and Wasm environments, including pointer contracts, associated accounts, and transactions.
Link and display pointer and original contracts for both fungible and non-fungible tokens.
Recognize and display both associated and non-associated accounts.
Monitor and track all transactions occurring on the Sei Network.
Get detailed information about blocks, including their contents and creation details.
View detailed information about accounts, including balances and transaction history.
Explore both fungible tokens and NFTs on the network.
Access information about validators, their performance, and status.
Verify and interact with smart contracts deployed on Sei Network.
Track Inter-Blockchain Communication (IBC) relayers and their activities.
* Stay updated with governance proposals and their outcomes.
Verifying your deployed contract using flattened source code, JSON input and more
And **Others:** Public & private tags, API keys, Export CSV, etc.
Dive into Seitrace for a comprehensive and real-time view of the Sei Network, leveraging the best of Sei ecosystem.
# My account
Source: https://docs.seitrace.com/profile/my-account
## **Features of Profile**
### **API Keys**
* **Purpose**: Obtain an individually rate-limited API key for accessing various services.
* **Usage**: Useful for managing and monitoring API usage, ensuring fair access and preventing abuse.
Generate API keys for your Seitrace Insights account in a few simple steps
### **Custom ABI**
* **Purpose**: Useful for testing and debugging smart contracts.
* **Usage**: Can be used with both verified and unverified contracts, allowing developers to interact with their contracts in a customized manner.
Useful for debugging and testing newly deployed smart contracts.
### **How to Sign in**
1. **Accessing the Login**:
* On any page, click on the "Sign in" button.
2. **Sign in options**:
* **a. Email & Password**: Enter your registered email and password to log in.
* **b. Google account**: Use your Google account for a quick and secure login.
3. **Sign Up**:
* If you do not have an account yet, you can sign up for a new account.
### **After Signing in**
Once logged in, users can access advanced functions:
* **API Keys**: Request and manage API keys for personalized, rate-limited access.
* **Custom ABI**: Upload and use custom ABIs for interacting with smart contracts, whether they are verified or unverified.
By providing these features, users can enhance their experience and capabilities on the platform, leveraging tools for better development and operational efficiency.
# Private tags
Source: https://docs.seitrace.com/profile/private-tags
## **The Private Tags Feature:**
With this feature, you are able to tag any address on the SEI blockchain with a private name tag (and also a private note) for your personal reference (these name tags are only visible to you once you have logged in to your Seitrace account).
## **To use the Private Tags feature:**
### **Adding from Profile > Private Tags**
1. Log in at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Go to Profile > Private tags
3. Choose to add a tag for an Address or a Transaction
4. Click "Add address/transaction tag"
5. In the popup, fill out:
* Address or Transaction hash
* For addresses, you can include associated addresses if available
* Enter your private tag
* Add a note if desired
6. Click "Add tag"
Note: You can add up to 1000 tags total for both Addresses and Transactions.
### **Adding from Address/Contract or Transaction Details Page**
1. Log in at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Navigate to the specific address, contract, or transaction details page
3. Look for the option to add a private tag
4. In the popup:
1. Address/transaction field will be auto-filled
2. For addresses, you can include associated addresses if available
3. Enter your private tag
4. Add a note if desired
5. Click "Add address" to finalize
After adding a private tag, it will appear next to the address or transaction hash on the details page.
These methods allow you to organize and quickly identify important addresses or transactions on the Sei network with personalized tags.
# Watch list
Source: https://docs.seitrace.com/profile/watch-list
## **The Watch List Feature:**
* Allows users to track specific addresses
* Notifies users via email about incoming or outgoing transactions for listed addresses
* Supports both EVM and Native SEI addresses
## **To use the Watch List feature:**
### **Add from Profile > Watch list**
1. Log in to your account at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Navigate to Profile > Watch list
3. Click the "Add" button to create a new watch list entry
4. Enter the address you want to track in the "Address (0x.../sei...)" field. This can be a user address or smart contract address
5. If there's an associated address, you have the option to include it in your favorites
6. Add a note for the address if desired
7. Adjust notification settings according to your preferences
8. Click "Add address" to finalize
9. The address will be added to your watch list
### **Add from address/contract details page**
1. Log in to your account at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Navigate to the address or contract details page you want to add to your watch list
3. Look for and click on the star icon "☆"
4. A popup window will appear with the Address field automatically filled
5. If there's an associated address, you have the option to include it in your favorites
6. Add a note for the address if desired
7. Adjust notification settings according to your preferences
8. Click "Add address" to finalize
9. The address will be added to your watch list
# Sei Network
Source: https://docs.seitrace.com/sei-network
Sei is the fastest parallel blockchain.
## What is the EVM?
The EVM (Ethereum Virtual Machine) is used to process transactions in blockchains such as Ethereum. Most crypto native developers are extremely familiar with the EVM.
Unfortunately, the EVM is quite inefficient - on Ethereum L1, it's not able to process more than \~20 TPS.
This results in
* high transaction fees for users, often going into hundreds of dollars for simple transactions
* a restricted design space for developers, who are unable to build high performance applications
## What is parallelization?
Parallelization lets you process multiple things at the same time (i.e. in parallel). This is commonly used in software engineering to take advantage of modern hardware (which has multiple cores) to process multiple workstreams at the same time.
For Sei, parallelization is used to process multiple independent transactions at the same time.
## What are the benefits of Sei?
Sei represents a 100x improvement on the EVM. This will unlock an entirely new design space for application developers, and make the EVM much cheaper to access for normal people.
# Create Token
Source: https://docs.seitrace.com/tools/create-token
Launch your own ERC-20 token on Seitrace—free, fast deployment on Sei blockchain. Customize name, supply, and features in minutes. No code required.
Seitrace provides a free, user-friendly tool to create ERC-20 tokens directly on the Sei blockchain. This allows you to launch your own fungible token with full control over its identity, supply, and features. No coding required—simply fill out the form, connect your wallet, and deploy. Your token will be minted on the Sei Mainnet and visible in wallets and explorers.
**Key Benefits:**
* **Free Deployment**: No deployment cost, only gas fees
* **Customizable**: Set name, symbol, supply limits, and optional features like minting or burning.
* **Secure**: Built on Sei's high-performance EVM-compatible chain for fast, low-cost transactions.
* **Automatically Verified**: Contract is automatically verified on Seitrace immediately after successful deployment.
## **How to create token:**
### Step 1: Access the Token Creation Tool
1. Visit [seitrace.com](http://seitrace.com).
2. Navigate to the tool via one of these paths:
* From the main menu: Click More > Tools > Create Token.
* Direct link: [https://seitrace.com/tool/create-token](https://seitrace.com/tool/create-token).
3. Ensure you have a compatible wallet (e.g., MetaMask, Compass,...) installed and connected to the Sei Mainnet network. If not, switch to Sei Mainnet in your wallet settings.
### Step 2: Enter Basic Information
Fill in the required fields under Basic Information. These define your token's core identity and technical specs.
| **Field** | **Description** | **Requirements & Limits** |
| -------------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Token Name\* | The full name of your token (e.g., "SeiTrace"). This appears in wallets and exchanges. | - Any characters allowed (letters, numbers, symbols). - No leading spaces. - Maximum 64 characters. |
| Token Symbol\* | The short ticker symbol (e.g., "SEITR"). Used for trading and display. | - Only \[0-9] and \[A-Z] characters. - Maximum 10 characters. - Typically 3-5 characters (like BTC, ETH, USDT). |
| Type | The token standard. | - Fixed: ERC-20 (only supported standard). |
| Decimals\* | The number of decimal places for token precision (e.g., 18 allows fractions like 0.000000000000000001). | - Integer from 0 to 18. |
### Step 3: Configure Features (Optional)
Add optional functions to your token, such as minting new supply, burning tokens, or pausing transfers.
| **Feature** | **Description** | **How It Works (ON vs. OFF)** |
| ---------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Mintable | Allows the token owner (you) to create additional tokens after deployment. | - ON: Your token can grow beyond the initial supply. - OFF: No new tokens can be minted. |
| Burnable | Allows holders (including you) to permanently destroy tokens, reducing total supply. | - ON: Anyone can burn their tokens via standard ERC-20 functions. - OFF: Burning is not possible; supply remains fixed once minted. |
| Pausable | Allows the token owner to pause all transfers in emergencies (e.g., security issues). | - ON: You can pause/resume transfers contractually. - OFF: Transfers cannot be paused; always active. |
| Unlimited Supply | Enables infinite minting without a cap (requires Mintable to be ON). | - ON: No hard limit on total tokens. - OFF: Maximum Supply behaves based on Mintable toggle. |
### Step 4: Set Supply Details
These control how many tokens exist and how they're distributed.
| **Field** | **Description** | **Requirements & Limits** |
| ---------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Initial Supply\* | The number of tokens minted and assigned to your wallet at launch. | - Numbers only (e.g., 1000000). - Cannot exceed Maximum Supply (error shown if it does). |
| Maximum Supply | The total cap on tokens that can ever exist (only if Mintable is ON). | - Maximum input: Up to 5Q (5 × 10¹⁸, matching 18-decimal precision) |
### Step 5: Create the Token
At the bottom, click Create Token.
* Confirm the transaction in your wallet.
* Deployment takes \~10-30 seconds on Sei Mainnet.
* Success: You'll see a confirmation with your token's contract address. Add it to your wallet (e.g., MetaMask, Compass,...) using the address. You can also submit token information after creation.
* Token contract is automatically verified on Seitrace immediately after successful deployment.
# API for EVM contract verification
Source: https://docs.seitrace.com/verify-contract/api-for-evm-contract-verification
API For EVM Contract verification
apiURL:
* arctic-1: [https://seitrace.com/arctic-1/api](https://seitrace.com/arctic-1/api)
* pacific-1: [https://seitrace.com/pacific-1/api](https://seitrace.com/pacific-1/api)
* atlantic-2: [https://seitrace.com/atlantic-2/api](https://seitrace.com/atlantic-2/api)
# Custom ABI
Source: https://docs.seitrace.com/verify-contract/custom-abi
The Custom ABI feature is useful for debugging and testing newly deployed smart contracts. This feature can be used with verified or unverified contracts.
Once a custom ABI is added, the user can test methods using the Write Custom feature.
## **Add Custom ABI**
1. \[Login to My Account]\([https://seitrace.com/?chain=pacific-1\\](https://seitrace.com/?chain=pacific-1\\)) in Seitrace to get started. Once logged in:
1. Go to **Custom ABI** in the My Account menu.
2. Press the **Add Custom ABI** button
2. **Fill in the fields**.
1. **Smart Contract Address**. Enter the correct `0x` address of the deployed contract.
2. **Project Name**. Create a name for your own reference.
3. **Custom ABI**: Copy and paste in the ABI for the contract from your development environment (truffle, hardhat, remix etc) or if the contract is verified you can copy from Seitrace.
4. Press **Create custom ABI**.
3. \*\*Custom ABI added \*\*to the home screen. You can edit or remove current custom ABIs or add additional custom ABIs from here.
# Hardhat verification plugin
Source: https://docs.seitrace.com/verify-contract/hardhat-verification-plugin
Hardhat is a full-featured development environment for contract compilation, deployment and verification. The Hardhat Verification Plugin supports contract verification on Seitrace.
## **Get started**
1. **Install Hardhat**
If you are starting from scratch, create an npm project by going to an empty folder, running `npm init`, and following the instructions. Recommend npm 7 or higher.
**Once your project is ready:**
**npm instructions**
```
npm install --save-dev hardhat
```
**yarn instructions**
```
yarn add --dev hardhat
```
2. **Create a project**
Run `npx hardhat` in your project folder and follow the instructions to create ([more info here](https://hardhat.org/getting-started/#quick-start)).
3. **Install plugin**
Install the [hardhat-etherscan plugin](https://hardhat.org/plugins/nomiclabs-hardhat-etherscan.html) (requires **v3.0.0+).**
**npm**
```
npm install --save-dev @nomiclabs/hardhat-etherscan
```
**yarn**
```
yarn add --dev @nomiclabs/hardhat-etherscan
```
4. **Add plugin reference to config file**
Add the following statement to your `hardhat.config.js`.
Copy
```
require("@nomiclabs/hardhat-etherscan");
```
If using TypeScript, add this to your `hardhat.config.ts.` [More info on using typescript with hardhat available here](https://hardhat.org/guides/typescript.html#typescript-support).
```
import "@nomiclabs/hardhat-etherscan";
```
## **Config File**
Your basic [Hardhat config file](https://hardhat.org/config/) (`hardhat.config.js` or `hardhat.config.ts`) will be setup to support the network you are working on. In this example we use the Sokol test network and a `.js` file.
Here we add an RPC url without an API key, however some value is still required. You can use any arbitrary string. [More info](https://hardhat.org/plugins/nomiclabs-hardhat-etherscan.html#multiple-api-keys-and-alternative-block-explorers).
If you prefer, you can migrate to [hardhat-toolbox](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-toolbox) to use a plugin bundle.
```
import dotenv from "dotenv";
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";
import "tsconfig-paths/register";
import "@openzeppelin/hardhat-upgrades";
/**
* Config dotenv first
*/
dotenv.config();
/**
* Default hardhat configs
*/
const config: HardhatUserConfig = {
solidity: {
compilers: [
{
version: "0.8.20",
settings: {
optimizer: {
enabled: true,
runs: 200,
},
},
},
],
},
};
/**
* Extract env vars
*/
const privateKey = process.env.PRIVATE_KEY || "";
/**
* If private key is available, attach network configs
*/
if (privateKey) {
config.networks = {
sei_arctic_1: {
url: "https://evm-rpc.arctic-1.seinetwork.io/",
chainId: 713715,
accounts: [privateKey],
gas: "auto",
gasPrice: "auto",
},
};
}
/**
* Load etherscan key
*/
const seitraceKey = process.env.SEITRACE_KEY || "";
if (seitraceKey) {
config.etherscan = {
apiKey: {
sei_arctic_1: seitraceKey,
},
customChains: [
{
network: "sei_arctic_1",
chainId: 713715,
urls: {
apiURL: "https://seitrace.com/arctic-1/api",
browserURL: "https://seitrace.com"
}
},
],
};
}
export default config;
```
apiURL:
* arctic-1: [https://seitrace.com/arctic-1/api](https://seitrace.com/arctic-1/api)
* pacific-1: [https://seitrace.com/pacific-1/api](https://seitrace.com/pacific-1/api)
* atlantic-2: [https://seitrace.com/atlantic-2/api](https://seitrace.com/atlantic-2/api)
Set up env. file
```
PRIVATE_KEY="4c1a9ffd2dce9ed5b5f464c6b6a38efceb051855d123c9e6aeec751c35762d91"
SEITRACE_KEY="can-be-any-string"
```
* PRIVATE\_KEY: Wallet private key
* SEITRACE\_KEY: You can also use a random string
## **Deploy and Verify**
**Deploy**
```
npx hardhat run .\scripts\\deploy.multicall.ts --network sei_arctic_1
```
**Verify**
```
npx hardhat verify --network sei_arctic_1 "Constructor argument"
```
**Example**
```
PS D:\verify-contract> npx hardhat verify --network sei_arctic_1 0xaa338AbfB92e7476596D4cCb98b29700BDcA2a6E "0xc99259dE8f9ec4cd443C0CF5D45D547c513E03be"
Successfully submitted source code for contract
contracts/VuNFT721.sol:VuSEI721 at 0xaa338AbfB92e7476596D4cCb98b29700BDcA2a6E
for verification on the block explorer. Waiting for verification result...
Successfully verified contract VuSEI721 on the block explorer.
https://seitrace.com/address/0xaa338AbfB92e7476596D4cCb98b29700BDcA2a6E#code
```
## **Confirm Verification on Seitrace**
# Interacting with smart contracts
Source: https://docs.seitrace.com/verify-contract/interacting-with-smart-contracts
## **Use Seitrace to Read and Write to Smart Contracts**
Once a contract is verified, its methods are exposed, and direct interaction is possible through Seitrace.
## **Read contract**
Read actions allow you to check various contract attributes. Connecting a web3 wallet is required to make a query, but queries do not require a transaction or any gas costs.
1. **Find the contract address**:
* Locate and enter the contract address you want to interact with into the search bar on Seitrace.
2. **Navigate to the contract page**:
* Select the first option in the search results, which takes you to the token page.
* For more detailed information, click through to the contract page.
3. **Verify contract code**:
* Scroll down past the contract details to see if the code is verified (indicated by a checkmark ✅).
* If the code is not verified, you cannot read or write to the contract unless a verified contract with the same bytecode is found in the Seitrace database.
4. **Proxy Implementation**:
* If the contract is a proxy implementation, you will see options to read/write to the contract or the proxy. A proxy means the contract is upgradeable, and the admin can set a new proxy address for the primary contract if upgrades are needed.
5. **Interact with Contract Methods**:
* Various methods within the contract are visible. Some show current values, while others are queryable.
* For example, to query the `balanceOf` method:
* Fill out the `_owner` (address) field.
* Click on "Query".
* Seitrace will execute the query and return the result under the function.
## **Write Contract**
To write to a contract, follow similar steps as above but with the additional requirement of paying gas fees for transactions:
1. **Find and navigate to the contract**:
* Enter the contract address in the search bar.
* Click through to the contract page from the search results.
2. **Verify contract code**:
* Ensure the contract code is verified.
3. **Proxy Implementation**:
* If applicable, decide whether to interact with the contract or the proxy.
4. **Interact with contract methods**:
* Connect your wallet with MetaMask.
* Fill out the necessary fields for the method you wish to write to. (example on function \_safeMint)
* Click on "Write" and confirm the transaction in your wallet (Metamask).
* The transaction will be sent to the blockchain, and you will receive a transaction hash once completed.
# Seitrace UI
Source: https://docs.seitrace.com/verify-contract/seitrace-ui
Verification is available for both Solidity and Vyper contracts.
Currently, there are 6 methods for verification using the Seitrace UI.
Access function at: [https://seitrace.com/contract-verification](https://seitrace.com/contract-verification)
## **Smart Contract Verification with Seitrace**
1. Go to the Verify contract page *(Resources -> Verify contract(EVM))*
2. Enter in the contract address you received during deployment. The dropdown will show you several available verification options. Select the one you would like to use and continue.
* Solidity (Flattened source code)
* Solidity (Standard JSON input)
* Solidity (Multi-part files)
* Vyper (Contract)
* Vyper (Multi-part files)
* Vyper (Standard JSON input)
### **Solidity (Flattened source code)**
1. **Contract Address:** The `0x` address supplied on contract creation (added above)
2. **Is Yul contract:** Select if the contract is coded in Yul for efficiency.
3. **Include Nightly Builds**: Select if you want to show nightly builds.
4. **Compiler:** derived from the first line in the contract `pragma solidity X.X.X`. Use the corresponding compiler version rather than the nightly build.
5. \*\*EVM Version: \*\*Select the correct[ EVM version ](https://docs.blockscout.com/for-developers/evm-version-information)if known, otherwise use default.
6. **Optimization Enabled:** If you enabled optimization during compilation, select and enter the run value. 200 is the Solidity Compiler default value. Only change if you changed this value while compiling.
7. **Enter the Solidity Contract Code:** You may need to flatten your solidity code if it utilizes a library or inherits dependencies from another contract. We recommend [hardhat ](https://hardhat.org/hardhat-runner/docs/advanced/flattening)or the [POA solidity flattener](https://github.com/poanetwork/solidity-flattener).
8. **Add Contract Libraries:** Enter the name and 0x address for any required libraries called in the .sol file. You can add multiple contracts with the "+" button.
9. Click the `Verify and Publish` button.
10. If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called `Read Contract`. The contract name will now appear in Seitrace with any transactions related to your contract.
### **Solidity (Standard JSON input)**
[More information on JSON input is available here](https://docs.soliditylang.org/en/latest/using-the-compiler.html#input-description)
1. **Include nightly builds**. You can choose **Yes** or **No** depending on your compiler.
2. **Compiler.** Choose the compiler version used to compile your smart contract. If you selected yes for nightly builds, use the compiler version rather than the build.
3. **Standard Input JSON.** Upload your Standard Input JSON file. File should follows solidity [format](https://docs.soliditylang.org/en/latest/using-the-compiler.html#input-description) and all the sources must be in Literal Content format, not a URL.
Click the **Verify & publish** button and wait for the response.
### **Vyper Contract**
1. **Contract Name:** Name assigned to the contract.
2. **Compiler**: Select the compiler version used in the source code.
3. \*\*EVM Version: \*\*Select the correct[ EVM version ](https://docs.blockscout.com/for-developers/evm-version-information)if known, otherwise use default.
4. **Contract Code:** Copy and paste the contract code
5. Click the `Verify and Publish` button.
If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called `Read Contract`. The contract name will now appear in BlockScout with any transactions related to your contract.
### **Vyper Multi-part files and standard json input**
See the information above.
## **Troubleshooting**
If you receive the dreaded `There was an error compiling your contract` message this means the bytecode doesn't match the supplied sourcecode. Unfortunately, there are many reasons this may be the case. Here are a few things to try:
1. Double check the compiler version is correct.
Check all version digits - for example 0.5.1 is different from 0.5.10
2. Check that an extra space has not been added to the end of the contract. When pasting in, an extra space may be added. Delete this and attempt to recompile.
3. Copy, paste, and verify your source code in Remix. You may find some exceptions here.
# Verify contract EVM
Source: https://docs.seitrace.com/verify-contract/verify-contract-evm
Verifying your deployed contract using flattened source code, JSON input, Sourcify and more
Verifying your deployed contract ensures transparency and trust by making the source code publicly available and verifiable. Seitrace supports verification for both Solidity and Vyper contracts, with seven methods available through the Seitrace UI.
## **Benefits of Verification**
* **Transparency**: Publicly available source code.
* **Trust**: Community can verify the contract's functionality.
* **Security**: Greater confidence in the contract's integrity.
## **Guide to verify your contract on Seitrace**
Verification is available for both Solidity and Vyper contracts on Seitrace UI
The Hardhat Verification Plugin supports contract verification on Seitrace.
Useful for debugging and testing newly deployed smart contracts.
The list apiURL For EVM Contract verification on mainnet, testnet and devnet
3. Scroll down to the "Free Trial" section.
4. Click on the "Get started now" button.
5. Confirm the activation of your trial package when prompted.
6. You will see a success message once the activation is complete.
After activation, you can access the API Keys management section.
In the API Keys management, you can create new API keys for use with the service.
3. In the popup window, enter your "App name"
4. Click "Create API Key"
5. Copy the generated key for use in your application
## **Important Notes:**
* There is a limit of 3 API keys per user account
* If your API credits expire or are exhausted, your account reverts to "Regular" status
* API calls made with keys from a "Regular" account will cease to function
Remember to store your API key securely and never share it publicly.
## Key Features
* **API Credit System**: Users purchase API credits to utilize the service. The credit has an expiration date.
* **Credit Packages**: Users can buy additional credits in packages to extend their usage & exprie date.
* **Expiration and Exhaustion**: Once credits expire or are exhausted, users revert to regular status and cannot access the API until credits are replenished.
## Packages
* **Free Trial**: A 90-day trial package for new users.
* **Paid Packages**:
* Insights 30D
* Insights 90D
* Insights 180D
* Insights 360D
* Custom packages are available through private deals.
## Getting Started
## **Payment methods**
In the initial phase, we support cryptocurrency payments. You can transfer funds to our company's wallet on the following networks:
* TRON
* Ethereum
* Polygon
* SEI
Supported currencies:
* USDC
* USDT
## **After payment**
Upon successful payment verification, we will:
1. Activate your chosen package.
2. Notify you via email.
You can then start using the API by creating your API keys in your account dashboard.
The Token details page includes the following basic information about the token:
* **Price**: The current price of the token.
* **Full diluted market cap**: The market capitalization of the token.
* **Max total supply**: The maximum total supply of the token.
* **Holders**: The number of addresses holding the token.
* **Transfers**: The total number of transfers made with the token.
* **Contract information**: Details about the token contract, indicating whether it is an original or a pointer or just the normal token without pointer.
* **Original contract address**: The address of the original contract.
* **Pointer contract address**: The address of the pointer contract, if applicable.
* **Decimals**: The number of decimal places the token supports.
## **Token Transfers List**
Display a list of recent token transfers,
## **Token Holders**
The token holders section displays a list of addresses holding a specific token on the SEI blockchain. The display adapts depending on whether the token uses pointers or not.
* **Without pointer**: If the token does not include a pointer, it shows only one type of address (either EVM or Native SEI).
* **With pointer**: If the token includes a pointer, it shows both the EVM and Native SEI addresses of the owner.
## **Contract information**
Provide detailed information about the token contract
# Fungible tokens
Source: https://docs.seitrace.com/assets/fungible-tokens/tokens
The SEI blockchain supports various standards for fungible tokens across both EVM and Native SEI environments.
## **Supported Token Standards**
* **EVM**: ERC-20
* **Native SEI**:
* CW-20
* Native Token (SEI)
* IBC Tokens
## Tokens
The Tokens page provides an overview of all fungible tokens on the SEI blockchain, including those on both EVM and Native SEI. This page allows users to explore and view details about each token.
**Key features**
* **Token list**:
* Display a comprehensive list of fungible tokens available on the SEI blockchain.
* Each row in the token list includes the following information: Token & its address, the pointer/original of that token, type of token, price, Circulating market cap and the number of holders.
* **Filter and search**: Users can filter tokens by EVM/Native SEI and search for specific tokens by name or symbol or address.
* **Token details**: Users can click on each token to view detailed information.
## **Inventory**
Display the inventory of NFTs within the collection. For collections with pointers, show the associated address of the owner alongside each NFT and for collection without pointers, do not show the associated address.
## **NFT Transfers**
Display a list of recent NFT transfers within the collection, including:
* Transaction hash & its associated trx hash (if having) & timestamp
* Type & method of transaction
* From
* To
* Token ID
## **Token Holders**
The collection holders section displays a list of addresses holding NFTs in a specific collection on the SEI blockchain. The display adapts depending on whether the collection uses pointers or not.
* **Without pointer**: If the collection does not include a pointer, it shows only one type of address (either EVM or Native Sei).
* **With pointer**: If the collection includes a pointer, it shows both the EVM and Native Sei addresses of the owner.
## **Contract information**
Provide detailed information about the token contract.
### **Filter and search:**
* Users can filter collections by EVM/Native Sei & filter by type of collection and search for specific collections by name or address.
### **Collection Details:**
* Users can click on each collection to view detailed information.
## **Owner Information**
* **Owner address**: The address of the current owner of the NFT.
* **Associated address**: If the NFT is part of a collection that includes pointers, display both the EVM and Native Sei addresses of the owner.
## **Properties & description:**
* Key attributes and traits of the NFT.
* A brief description of the NFT.
## **Item activities**
The item activities tab displays a history of activities related to the NFT. If the NFT is a pointer, it shows activities from both the original and pointer contracts.
* **Trx hash & it's associated trx hash (if having) & included the timestamp**
* **Activity type**: The type of activity (e.g., transfer, sale).
* **From address**: The address that initiated the activity.
* **To address**: The address that received the activity.
## **Metadata**
The Metadata tab provides detailed metadata for the NFT, including:
* **Metadata attributes**: Key-value pairs detailing specific properties of the NFT.
* **Metadata URL**: The URL where the metadata is stored (if applicable).
# Account details
Source: https://docs.seitrace.com/browsing-the-site/account-details
On the SEI blockchain, accounts have two wallet addresses: an EVM-compatible address (0x...) and a COSMOS-compatible address (sei...). These addresses correspond to the same account but operate on different layers of the SEI ecosystem.
## **Address association**
* **Separate accounts**: When the EVM and Native SEI (COSMOS) addresses are not associated, they are displayed as separate accounts.
* [**Associated accounts**](/evm-wasm/associated-accounts): Once the addresses are associated, they are displayed synchronously on a single interface. This means that regardless of which address you are viewing, you can see the transaction history, token holdings, and SEI balance for both addresses. The SEI balance is synchronized across both addresses.
### **Account details display**
The account details page includes the following information:
* **SEI balance**:
* Before association: Each address (0x... and sei...) displays its own separate SEI balance.
* After association: The SEI balance is synchronized and calculated as the combined total of both addresses at the time of association. This synchronized balance is displayed for both addresses.
* **Token holdings**: A list of tokens held by the account, including balances and details for both EVM and COSMOS tokens.
* **Transaction history**: A comprehensive history of all transactions involving the account, including both EVM and COSMOS transactions.
* **Gas used**: The total amount of gas used by the account in its transactions.
* **Internal transactions**: Transfers of SEI carried out through smart contracts, providing deeper insights into the account's activity.
By presenting this information in a unified view, users can easily manage and monitor their accounts regardless of the underlying address type, ensuring a seamless and integrated experience on the SEI blockchain.
# Blocks
Source: https://docs.seitrace.com/browsing-the-site/blocks
## **Blocks list**
The Blocks page provides a comprehensive view of all blocks in the SEI ecosystem, offering essential statistics and detailed information about each block.
### **Basic stats**
Display key statistics about the blocks:
* **Block height**: The current height of the blockchain, indicating the total number of blocks.
* **Block time**: The average time taken to produce a new block.
### **Blocks list**
Each row of block includes the following data:
* **Block number & time**: The unique identifier of the block and the timestamp when it was created.
* **Validator**: The validator that verified and added the block to the blockchain.
* **Txn count**: The number of transactions included in the block.
* **Gas used**: The total amount of gas used by the transactions in the block.
* **Reward SEI**: The reward in SEI given to the validator for producing the block.
By organizing this information clearly, users can easily navigate and understand the performance and activity of Sei Network through its blocks.
## **Block details**
Seitrace provides basic data about each block:
* \*\*Details tab: \*\*display the following detailed fields: Block height, Size, Timestamp, Transactions (count), Validated by, Gas usage, Gas limit, Base fee per gas, Block hash and parent hash. Each field is defined by the included tooltip.
* **Transactions tab**: displays a list of transactions included in the block both EVM & Native Sei.
By organizing this information clearly, users can easily navigate and understand the performance and activity of Sei Network through its blocks and the transactions they contain.
# Code ID
Source: https://docs.seitrace.com/browsing-the-site/code-id
Doc coming soon
# Contract details
Source: https://docs.seitrace.com/browsing-the-site/contract-details
The contract details page provides comprehensive information about a contract on the SEI blockchain. Contracts are treated similarly to addresses/accounts but include additional contract-specific details.
## Common features with [**addresses (accounts)**](/browsing-the-site/account-details)
Contracts share several features with regular addresses, such as:
* **Transaction history**: Displaying all transactions involving the contract.
* **Token holdings**: Listing tokens held by the contract.
* **Balance SEI**: Showing the SEI balance of the contract.
* **Internal txns**: Displaying internal transactions, which are SEI transfers carried out via smart contracts.
* **Associated account**: Supporting associated accounts, allowing users to view synchronized information across both EVM and COSMOS addresses. Learn more here.
## **Contract-specific features**
In addition to the common features, the contract details page includes:
* \*\*More information: \*\*Token name, Contract name, Contract creator, Contract type, Implementation
* **Logs tab**: Displaying logs generated by the contract.
* **Detailed contract information**: Providing in-depth details about the contract, such as its creation code, deployed bytecode, verification status and interaction between wallet and contract.
## **EVM contract verification status**
EVM contracts can have three verification statuses:
1. **Unverified**:
* **Details**: Users can see the Contract Creation Code and Deployed ByteCode.
* **Interaction**: Users need to verify and publish the contract to interact with it.
2. **Partial Match (Partially Verified)**:
* **Details**: Users can see partially matched source code, ABI (Application Binary Interface), and other contract details. This indicates that some parts of the contract match the source code provided, but not entirely. User can continue to [Verify & publish](/browsing-the-site/verified-contracts) for exact match
* **Interaction**: Users can interact with the contract, but some functionality may be limited due to partial verification.
3. **Exact Match (Fully Verified)**:
* **Details**: Users can see the fully verified source code, ABI, and complete contract details. This indicates that the contract's source code exactly matches the deployed bytecode.
* **Interaction**: Users can fully interact with the contract, utilizing all its functionalities.
## **Native SEI Contracts (COSMOS)**
Currently, contract verification for Native SEI (COSMOS) contracts is not supported.
## **Visual indicators**
* **Verified contracts**: Use an icon with a green checkmark on a green background to indicate a verified contract.
* **Unverified contracts**: Use a gray icon to indicate an unverified contract.
# Homepage
Source: https://docs.seitrace.com/browsing-the-site/homepage
This is the main window when users interact with Seitrace for the first time.
On the homepage, users are greeted with a comprehensive overview of the Sei ecosystem, featuring:
* **Basic stats:** Instantly view key statistics such as total transactions, blocks, TPS, average block time, total stake, and active accounts on the Sei Network.
* **Price information:** Stay updated with the latest SEI price, real-time market cap, and daily transaction volume, all visualized with dynamic charts.
* **Global search toolbar:** Access a powerful search tool for quickly finding addresses, transaction hashes, tokens, NFT collections, and more across the network.
* **Top earnings:** See top-earning pools by APR and TVL, helping users discover the most rewarding DeFi opportunities on Sei.
* **Latest blocks:** Recent blocks for both EVM and Native Sei. Users can view[ all the blocks ](/browsing-the-site/blocks)displayed on the Sei Network by clicking on the "View All" button.
* **Latest transactions:** Recent transactions for both EVM and Native Sei. Users can [view all the transactions ](/browsing-the-site/transactions)displayed on the Sei Network by clicking on the "View All" button.
* **Airdrops:** Access the latest airdrop campaigns and opportunities.
* **Validators:** Get an overview of leading validators, their voting power, and staking APR, with options to view the full validator list.
* **SEI Tools:** Quickly access essential tools, including token transfers, multisender, address book, SEI faucets, and profile management for seamless navigation and interaction within the Sei ecosystem.
This unified homepage ensures that users can monitor network health, market trends, and personal opportunities with ease—all from a single, intuitive homepage.
# IBC Relayers
Source: https://docs.seitrace.com/browsing-the-site/ibc-relayers
## IBC Relayers
List of IBC Relayers interacting with SEI Blockchain.
### **Statistics**
* **Connected Chains**: The total number of chains connected to the SEI blockchain via IBC.
* **Total Channels**: The number of channels that SEI blockchain connected to other chains via IBC.
* **Total Send**: The total number of transactions executed to send tokens via IBC relayers.
* **Total Receive**: The total number of transactions executed to receive tokens from IBC relayers.
### **All connected chains**
This section lists all chains connected to the SEI blockchain within the Cosmos ecosystem. Each entry includes:
* **Chain**: The name and identifier of the chain.
* **Total**: The number of transactions executed via the relayer between the SEI blockchain and the chain, including successful, failed, and pending transactions.
* **Receive**: The number of asset transactions received via the relayer, including successful, failed, and pending.
* **Send**: The number of asset transactions sent via the relayer, including successful, failed, and pending.
* \*\*Status: \*\*The current status of the connection between the SEI blockchain and the chain.
* **Channels**: The number of active channels versus the total connected channels between the SEI blockchain and the chain.
Users can filter by status or search by chain name or chain ID.
Clicking on a chain provides detailed information about the relayer.
## **Relayer details**
The Relayer Details provides information about the list of channels and their status.
Each entry includes:
* **Channel (Sei)**: The channel from the Sei blockchain.
* **Channel (Connected Chain)**: The channel from the connected blockchain.
* **Status**: The current status of the channel connection.
* **Operating Since**: The date the channel started operating.
* **Total**: The number of transactions executed via the channel, including successful, failed, and pending.
* **Received**: The number of asset transactions received via the channel, including successful, failed, and pending.
* **Sent**: The number of asset transactions sent via the channel, including successful, failed, and pending.
## **Channel details**
### **Overview Information**
* **Connected Channel**: Displays the name and status of the channel connection.
* **Counterparty**: The channel from the connected blockchain.
* **Operating Since**: The date the channel started operating.
* **Total Transactions**: The number of transactions executed via the channel, including successful, failed, and pending.
* **Client ID**: The identifier Tendermint associated with the channel.
### **Transfer assets Tab**
This tab displays assets transferred through the channel:
* **IBC Sending Assets**: Lists assets, quantities, and the number of transfers from Sei to the connected chain.
* **IBC Receiving Assets**: Lists assets, quantities, and the number of transfers received from the connected chain to Sei.
### **Transactions Tab**
Displays a list of transactions transferring in and out of the Sei blockchain via the channel.
# Proposals
Source: https://docs.seitrace.com/browsing-the-site/proposals
The navigation field in docs.json defines the pages that go in the navigation menu
## **Proposal list page**
### **Statistics**
* **Total Proposals**: Displays the total number of proposals submitted on the SEI blockchain.
* **Active Proposals**: Shows the number of proposals currently open for voting.
* **Passed**: Indicates the number of proposals that have been approved.
* **Rejected & Failed**: Lists the number of proposals that were either rejected or failed.
### **Active Proposals**
This section lists all proposals currently open for voting, allowing users to participate in the decision-making process.
### **All proposals**
This section includes all proposals from the SEI blockchain, their status includes:
* **In Deposit Period**: Proposals awaiting sufficient deposits.
* **In Voting Period**: Active proposals available for voting.
* **Passed**: Proposals that have been approved.
* **Rejected**: Proposals that have been turned down.
* **Failed**: Proposals that did not pass.
* **Not Enough Deposit**: Proposals lacking the required deposit.
Each proposal entry includes:
* **ID**: The unique identifier of the proposal.
* **Title & Type**: The name and type of the proposal.
* **Status**: The current state of the proposal.
* **Voting Ends**: The deadline for voting.
* **Proposed By**: The address of the proposer.
Users can click "View" to see more details of each proposal.
User can also filter by status or search by proposal ID or proposal title.
## **Proposal details**
### **Overview Information**
* **Proposal ID**: The unique identifier of the proposal.
* **Proposal Name**: The name of the proposal.
* **Status**: The current state of the proposal.
* **Most Vote On**: Shows the option with the most votes: Yes, No, Veto, Abstain.
* **Turnout/Quorum**: The participation rate in the voting process.
* **Type**: The type of proposal.
* **Create Tx**: The transaction hash where the proposal was created.
* Vote options and their voted:
* Yes: Agree with the proposal.
* No: Disagree with the proposal.
* No, with Veto: Strongly disagree with the proposal and request the deposit to be burned.
* Abstain: Choose not to vote either for or against the proposal but still participate in the governance process.
### **Details Tab**
Displays detailed information about the proposal: **Title**, Type, Description, Details, Voting Start, Voting End, Submit Time, Deposit End, Total Deposit
### **Votes Tab**
* \*\*Recent Votes: \*\*Lists recent votes from users and validators. Includes each address's vote choice and transaction hash for details.
* \*\*Validator Votes: \*\*Displays all validators and their votes. Shows each validator's vote choice and transaction hash for further details.
### **Depositors tab**
Shows a list of depositors and their deposit amounts. Includes transaction hashes for each deposit, allowing for detailed exploration.
# Search bar
Source: https://docs.seitrace.com/browsing-the-site/search-bar
The Search bar allows you to search for tokens, addresses, blocks, and transaction trackings in a clean and easy-to-follow manner.
* **Search tokens**:
* Users can type the token name, collection name, or token address.
* Support to display the verified token during searches.
* **Search addresses**:
* Users can type the name of a contract, account label, or the name of a token related to the contract.
* Enter the correct address
* Support pointer contract search
* **Search blocks**: Users can search by block number.
* **Search transactions**: Users can search by transaction hash.
* **Support recent searches**: Quickly access your recent searches for convenience.
# Top accounts
Source: https://docs.seitrace.com/browsing-the-site/top-accounts
The Top Accounts page highlights the accounts with the highest SEI balance, providing insights into the wealth distribution within the SEI ecosystem.
## Account list
Provide a detailed list of the top accounts sorted by SEI balance. Each entry should include:
* **Rank**: The rank of the account based on SEI balance.
* **EVM address**: The account's EVM address.
* **Native address**: The account's Native SEI address.
* **Public tag**: A public label of the account (if available).
* **Total balance SEI**: The current SEI balance held by the account.
* **Percentage**: The percentage of the total SEI supply held by the account.
* **Txn count**: The total number of transactions conducted by the account.
By organizing this information clearly, users can easily navigate and understand the distribution of SEI balances across the top accounts, as well as identify accounts with both EVM and native addresses, ensuring data synchronization is evident.
# Transactions
Source: https://docs.seitrace.com/browsing-the-site/transactions
## Transaction list
### **Basic Stats**
Display essential statistics about transactions:
* **Completed transactions**: The number of transactions with success status.
* **Total transactions**: The total number of transactions including: pending, dropped, replaced, failed and success status.
### **Transaction list**
Provide a comprehensive list of transactions, covering both EVM and Native SEI. Each transaction entry should include:
* **Transaction hash**: The unique identifier of the transaction.
* [**Associated transaction hash**](/evm-wasm/associated-transactions): The hash of the associated transaction, if applicable.
* **Status**: The current status of the transaction (e.g., pending, success, failed).
* **Type & method**: The type of the transaction (e.g., coin transfer, token transfer, contract call, contract creation, token burning, token creation, token minting, transaction) and method of transaction.
* **Block**: The block number in which the transaction is included.
* **From/To**: The sender and recipient addresses of the transaction.
* **SEI Value**: The value transferred in SEI.
* **Fee SEI**: The transaction fee in SEI.
### **Tabs**
* **Tab EVM**: Displays transactions on the EVM.
* **Tab Native SEI**: Displays transactions on Native SEI.
By organizing transactions into these tabs and providing detailed information, users can easily navigate and understand transaction activities across both environments.
## **Transaction details**
### **EVM transaction**
### **On EVM transactions, show:**
* **Details tab:** display the following detailed fields: [Associated trx hash](/evm-wasm/associated-transactions), Transaction hash, Status and method, Block, Timestamp, Transaction action, From, To/Interacted with contract, Token transferred, Token burnt, Token minted, Value, Transaction fee, Gas price, Gas usage & limit by txn, Gas fees, Burnt fee, Raw input and Decoded input data. Each field is defined by the included tooltip.
* **Token transfers tab**: display list of token transfers transactions
* **Internal txns tab**: Show the transfers of SEI carried out through a smart contract as an intermediary.
* **Logs tab**: Display the logs exposed from the blockchain, detailing events and actions taken during the transaction.
* **State tab**: Display the changes in balance resulting from the transaction.
By organizing these details into clear categories, users can easily access and understand the comprehensive information related to each EVM transaction.
### **Native SEI transaction**
### **On Native SEI transactions, show:**
* **Details tab:** display the following detailed fields: [Associated trx hash](/evm-wasm/associated-transactions), Transaction hash, Status and method, Block, Timestamp, Memo, Messages & their details, Signed by, Value, Transaction fee, Gas price, Gas usage & limit by txn. Each field is defined by the included tooltip.
* **Token transfers tab**: display list of token transfers transactions
* **Logs tab**: Display the logs exposed from the blockchain, detailing events and actions taken during the transaction.
By organizing these details into clear categories, users can easily access and understand the comprehensive information related to each SEI transaction.
# Validators
Source: https://docs.seitrace.com/browsing-the-site/validators
## **Validator list**
The Validators page provides a comprehensive view of the validators in the SEI ecosystem, offering essential statistics and detailed information about each validator.
### **Basic stats**
Display key statistics about the validators:
* **Total validators**: The total number of validators in the network.
* **Active validators**: The number of validators currently active and participating in consensus.
* **Inactive validators**: The number of validators that are currently inactive.
* **Jailed validators**: The number of validators that have been jailed due to misbehavior or failing to meet the network requirements.
### **Validator list**
Provide a searchable and filterable list of validators with the following features:
* **Filter by status**: Users can filter the list to show only active, inactive, or jailed validators.
* **Search by validator name or address**: Users can search for a validator by its name or operator address.
Each row of validator includes the following data:
* **Validator name & operator address**: The name of the validator and its operator address.
* **Voting power**: The voting power of the validator, indicating its influence in the network.
* **Commission**: The commission rate charged by the validator for its services.
* **Participation**: The level of participation by the validator in the consensus process.
* **Uptime**: The uptime percentage, showing how reliably the validator has been online.
By organizing this information clearly, users can easily navigate and understand the performance and status of validators within the Sei Network.
## **Validator details**
V1.0.0
In this version, Seitrace provides basic data about each validator, with more detailed information supported in future updates.
* **Validator Name**
* **Voting power in SEI & percentage**: The amount of SEI and the percentage of total voting power.
* **Status**: The current status (active, inactive, jailed).
* **Delegators**: The number of delegators supporting the validator.
* **Commission**: The commission rate.
* **Max Rate**: The maximum commission rate.
* **Max Change Rate**: The maximum rate at which the commission can change.
* **Updated**: The last time the validator's information was updated.
* **Addresses**: account address, operator address, consensus address, and hex address.
By organizing this information clearly, users can easily navigate and understand the performance and status of validators within the Sei Network. Detailed data will be expanded in future versions to provide even more insights into each validator's operations and performance.
# Verified contracts
Source: https://docs.seitrace.com/browsing-the-site/verified-contracts
In version 1.0.0, we support displaying verified contracts for EVM only. Seitrace will support Native SEI contract in upcoming version.
## **Basic stats**
Display basic statistics about contracts:
* **Total contracts (EVM)**: The total number of contracts on EVM.
* **Verified contracts (EVM)**: The number of verified contracts on EVM.
## **Latest verified contracts**
Display a list of the latest verified contracts. Basic information includes:
* **Contract name & address**: The name of the contract and its address.
* **Balance SEI**: The SEI balance of the contract (supported for associated).
* **Txs**: The number of transactions involving the contract.
* **Compiler/Version**: The compiler and version used to create the contract.
* **Verification time (Verified)**: The time when the contract was verified.
## **Filtering and Search**
Users can:
* **Filter by compiler**: Filter the list of contracts by compiler.
* **Search by contract name or its address**: Search for contracts by their name or address.
# Product updates
Source: https://docs.seitrace.com/changelog/product-updates
Keep track of changes and updates
### **🚀 Seitools — Do More, Faster**
* 🪙 [Create Token](https://seitrace.com/tool/create-token): Launch new tokens with a guided setup.
* 📌 [Deploy Pointer](https://seitrace.com/tool/deploy-pointer): Create and manage token pointers for seamless tracking.
* 🔁 [Swap Token](https://brrr.fun/swap): Swap assets with a smoother, more reliable flow.
### 💰 Earnings — New LP Staking
🟡 Kura LP Staking: Stake Kura LP tokens and monitor rewards directly in Earnings.
### 🖼️ NFTs — Clearer Market Signals
* 📉 Floor Price % Change: New column showing percentage changes in floor price.
* 🔎 Sorting & Filtering: Sort/filter by floor, % change, volume, and more.
### ⚙️ Seitrace MCP
Bring Seitrace data to [AI via Model Context Protocol](https://seitrace.com/mcp).
### 📊 Performance & Reliability
* ⚡ Faster load times and smoother navigation.
* 🛠️ Fixed minor bugs
**Try SeiTrace 1.14.0 today and explore these upgrades across Seitools, Earnings, MCP, and NFTs!**
* **Multisender:** The multisender tool now charges a fee of 0.05 SEI per address.
* **NFT Data:** We added a **Floor Price** for NFT collections and **Price** for individual NFT IDs, giving you more market insights.
* **Marketplace List:** Find a new, centralized list of all supported marketplaces.
* **API Button:** An **API** button is now available on relevant pages for quick access to our documentation.
* **Project Submission:** You can now include **smart contracts** when submitting a new project.
* **Account Filters:** Filter accounts by category for easier tracking and analysis.
* **Name Tagging:** Easily add or update custom names for contracts and accounts for a personalized view.
* **Project Directory:** A comprehensive directory of Sei ecosystem projects, with the option to submit and update project information.
* **API Docs**: Access the API documentation quickly and conveniently from every page.
Seitrace recognizes and displays both associated and non-associated accounts, providing comprehensive visibility into account activities. Here’s how it works:
* **Associated accounts**: Seitrace identifies and links the two addresses, displaying them as a single account with merged transaction history, combined balances and token holdings.
* **Non-associated accounts**: For accounts that are not yet associated, Seitrace displays the separate EVM and Native Sei addresses and their respective data.
# Associated transactions
Source: https://docs.seitrace.com/evm-wasm/associated-transactions
On Sei Network, certain transactions specifically establish an association between the signer's Sei address and their EVM address on-chain. Seitrace supports and displays these association transactions to provide transparency and facilitate easier management for users.
# EVM <> Wasm interoperability
Source: https://docs.seitrace.com/evm-wasm/evm-wasm
Seitrace supports seamless EVM and Wasm interoperability.
## EVM \<> Wasm Interoperability
EVM and Cosmos based applications co-exist on Sei, but live in different execution environments. This creates a challenge for users, who use wallets that typically only support a single execution environment. Likewise for devlelopers, existing tooling and libraries can only interact with either EVM or Wasm (Think EthersJS vs CosmJS).
To bridge the gap between EVM and Wasm, Sei has introduced novel interoperability features, allowing for smooth and easy interactions between both environments. These features will enable all contracts deployed to Sei to be accessible by tools and wallets from both environments.
Read more: [https://v2.docs.sei.io/interoperability/overview](https://v2.docs.sei.io/interoperability/overview)
## Supports
On Seitrace, we also supported for:
On Seitrace, we link and display pointer and original contracts for both fungible tokens (CW-20 & ERC-20) and non-fungible tokens (CW-721 & ERC-721).
# Introduction
Source: https://docs.seitrace.com/index
Welcome to the Seitrace documentation page
## What is Seitrace?
> Seitrace is a Block Explorer and Analytics Platform for Sei Network
**Seitrace** is the first explorer to support both the parallelized EVM and Native Sei (on Wasm). As the comprehensive explorer for the Sei Network, Seitrace offers a deep dive into real-time insights of the Sei Network. Track transactions, accounts, contracts, verify contracts, and explore network activity with our intuitive analytics tools.
## Key Features
1. **Accessing the Login**:
* On any page, click on the "Sign in" button.
2. **Sign in options**:
* **a. Email & Password**: Enter your registered email and password to log in.
* **b. Google account**: Use your Google account for a quick and secure login.
3. **Sign Up**:
* If you do not have an account yet, you can sign up for a new account.
### **After Signing in**
Once logged in, users can access advanced functions:
* **API Keys**: Request and manage API keys for personalized, rate-limited access.
* **Custom ABI**: Upload and use custom ABIs for interacting with smart contracts, whether they are verified or unverified.
By providing these features, users can enhance their experience and capabilities on the platform, leveraging tools for better development and operational efficiency.
# Private tags
Source: https://docs.seitrace.com/profile/private-tags
## **The Private Tags Feature:**
With this feature, you are able to tag any address on the SEI blockchain with a private name tag (and also a private note) for your personal reference (these name tags are only visible to you once you have logged in to your Seitrace account).
## **To use the Private Tags feature:**
### **Adding from Profile > Private Tags**
1. Log in at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Go to Profile > Private tags
3. Choose to add a tag for an Address or a Transaction
4. Click "Add address/transaction tag"
5. In the popup, fill out:
* Address or Transaction hash
* For addresses, you can include associated addresses if available
* Enter your private tag
* Add a note if desired
6. Click "Add tag"
Note: You can add up to 1000 tags total for both Addresses and Transactions.
### **Adding from Address/Contract or Transaction Details Page**
1. Log in at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Navigate to the specific address, contract, or transaction details page
3. Look for the option to add a private tag
4. In the popup:
1. Address/transaction field will be auto-filled
2. For addresses, you can include associated addresses if available
3. Enter your private tag
4. Add a note if desired
5. Click "Add address" to finalize
After adding a private tag, it will appear next to the address or transaction hash on the details page.
These methods allow you to organize and quickly identify important addresses or transactions on the Sei network with personalized tags.
# Watch list
Source: https://docs.seitrace.com/profile/watch-list
## **The Watch List Feature:**
* Allows users to track specific addresses
* Notifies users via email about incoming or outgoing transactions for listed addresses
* Supports both EVM and Native SEI addresses
## **To use the Watch List feature:**
### **Add from Profile > Watch list**
1. Log in to your account at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Navigate to Profile > Watch list
3. Click the "Add" button to create a new watch list entry
4. Enter the address you want to track in the "Address (0x.../sei...)" field. This can be a user address or smart contract address
5. If there's an associated address, you have the option to include it in your favorites
6. Add a note for the address if desired
7. Adjust notification settings according to your preferences
8. Click "Add address" to finalize
9. The address will be added to your watch list
### **Add from address/contract details page**
1. Log in to your account at [https://seitrace.com/auth/profile/](https://seitrace.com/auth/profile/)
2. Navigate to the address or contract details page you want to add to your watch list
3. Look for and click on the star icon "☆"
4. A popup window will appear with the Address field automatically filled
5. If there's an associated address, you have the option to include it in your favorites
6. Add a note for the address if desired
7. Adjust notification settings according to your preferences
8. Click "Add address" to finalize
9. The address will be added to your watch list
# Sei Network
Source: https://docs.seitrace.com/sei-network
Sei is the fastest parallel blockchain.
## What is the EVM?
The EVM (Ethereum Virtual Machine) is used to process transactions in blockchains such as Ethereum. Most crypto native developers are extremely familiar with the EVM.
Unfortunately, the EVM is quite inefficient - on Ethereum L1, it's not able to process more than \~20 TPS.
This results in
* high transaction fees for users, often going into hundreds of dollars for simple transactions
* a restricted design space for developers, who are unable to build high performance applications
## What is parallelization?
Parallelization lets you process multiple things at the same time (i.e. in parallel). This is commonly used in software engineering to take advantage of modern hardware (which has multiple cores) to process multiple workstreams at the same time.
For Sei, parallelization is used to process multiple independent transactions at the same time.
## What are the benefits of Sei?
Sei represents a 100x improvement on the EVM. This will unlock an entirely new design space for application developers, and make the EVM much cheaper to access for normal people.
# Create Token
Source: https://docs.seitrace.com/tools/create-token
Launch your own ERC-20 token on Seitrace—free, fast deployment on Sei blockchain. Customize name, supply, and features in minutes. No code required.
# API for EVM contract verification
Source: https://docs.seitrace.com/verify-contract/api-for-evm-contract-verification
API For EVM Contract verification
apiURL:
* arctic-1: [https://seitrace.com/arctic-1/api](https://seitrace.com/arctic-1/api)
* pacific-1: [https://seitrace.com/pacific-1/api](https://seitrace.com/pacific-1/api)
* atlantic-2: [https://seitrace.com/atlantic-2/api](https://seitrace.com/atlantic-2/api)
# Custom ABI
Source: https://docs.seitrace.com/verify-contract/custom-abi
The Custom ABI feature is useful for debugging and testing newly deployed smart contracts. This feature can be used with verified or unverified contracts.
Once a custom ABI is added, the user can test methods using the Write Custom feature.
## **Add Custom ABI**
1. \[Login to My Account]\([https://seitrace.com/?chain=pacific-1\\](https://seitrace.com/?chain=pacific-1\\)) in Seitrace to get started. Once logged in:
1. Go to **Custom ABI** in the My Account menu.
2. Press the **Add Custom ABI** button
2. **Fill in the fields**.
1. **Smart Contract Address**. Enter the correct `0x` address of the deployed contract.
2. **Project Name**. Create a name for your own reference.
3. **Custom ABI**: Copy and paste in the ABI for the contract from your development environment (truffle, hardhat, remix etc) or if the contract is verified you can copy from Seitrace.
4. Press **Create custom ABI**.
3. \*\*Custom ABI added \*\*to the home screen. You can edit or remove current custom ABIs or add additional custom ABIs from here.
# Hardhat verification plugin
Source: https://docs.seitrace.com/verify-contract/hardhat-verification-plugin
Hardhat is a full-featured development environment for contract compilation, deployment and verification. The Hardhat Verification Plugin supports contract verification on Seitrace.
## **Get started**
1. **Install Hardhat**
If you are starting from scratch, create an npm project by going to an empty folder, running `npm init`, and following the instructions. Recommend npm 7 or higher.
**Once your project is ready:**
**npm instructions**
```
npm install --save-dev hardhat
```
**yarn instructions**
```
yarn add --dev hardhat
```
2. **Create a project**
Run `npx hardhat` in your project folder and follow the instructions to create ([more info here](https://hardhat.org/getting-started/#quick-start)).
3. **Install plugin**
Install the [hardhat-etherscan plugin](https://hardhat.org/plugins/nomiclabs-hardhat-etherscan.html) (requires **v3.0.0+).**
**npm**
```
npm install --save-dev @nomiclabs/hardhat-etherscan
```
**yarn**
```
yarn add --dev @nomiclabs/hardhat-etherscan
```
4. **Add plugin reference to config file**
Add the following statement to your `hardhat.config.js`.
Copy
```
require("@nomiclabs/hardhat-etherscan");
```
If using TypeScript, add this to your `hardhat.config.ts.` [More info on using typescript with hardhat available here](https://hardhat.org/guides/typescript.html#typescript-support).
```
import "@nomiclabs/hardhat-etherscan";
```
## **Config File**
Your basic [Hardhat config file](https://hardhat.org/config/) (`hardhat.config.js` or `hardhat.config.ts`) will be setup to support the network you are working on. In this example we use the Sokol test network and a `.js` file.
Here we add an RPC url without an API key, however some value is still required. You can use any arbitrary string. [More info](https://hardhat.org/plugins/nomiclabs-hardhat-etherscan.html#multiple-api-keys-and-alternative-block-explorers).
If you prefer, you can migrate to [hardhat-toolbox](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-toolbox) to use a plugin bundle.
```
import dotenv from "dotenv";
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";
import "tsconfig-paths/register";
import "@openzeppelin/hardhat-upgrades";
/**
* Config dotenv first
*/
dotenv.config();
/**
* Default hardhat configs
*/
const config: HardhatUserConfig = {
solidity: {
compilers: [
{
version: "0.8.20",
settings: {
optimizer: {
enabled: true,
runs: 200,
},
},
},
],
},
};
/**
* Extract env vars
*/
const privateKey = process.env.PRIVATE_KEY || "";
/**
* If private key is available, attach network configs
*/
if (privateKey) {
config.networks = {
sei_arctic_1: {
url: "https://evm-rpc.arctic-1.seinetwork.io/",
chainId: 713715,
accounts: [privateKey],
gas: "auto",
gasPrice: "auto",
},
};
}
/**
* Load etherscan key
*/
const seitraceKey = process.env.SEITRACE_KEY || "";
if (seitraceKey) {
config.etherscan = {
apiKey: {
sei_arctic_1: seitraceKey,
},
customChains: [
{
network: "sei_arctic_1",
chainId: 713715,
urls: {
apiURL: "https://seitrace.com/arctic-1/api",
browserURL: "https://seitrace.com"
}
},
],
};
}
export default config;
```
apiURL:
* arctic-1: [https://seitrace.com/arctic-1/api](https://seitrace.com/arctic-1/api)
* pacific-1: [https://seitrace.com/pacific-1/api](https://seitrace.com/pacific-1/api)
* atlantic-2: [https://seitrace.com/atlantic-2/api](https://seitrace.com/atlantic-2/api)
Set up env. file
```
PRIVATE_KEY="4c1a9ffd2dce9ed5b5f464c6b6a38efceb051855d123c9e6aeec751c35762d91"
SEITRACE_KEY="can-be-any-string"
```
* PRIVATE\_KEY: Wallet private key
* SEITRACE\_KEY: You can also use a random string
## **Deploy and Verify**
**Deploy**
```
npx hardhat run .\scripts\
# Interacting with smart contracts
Source: https://docs.seitrace.com/verify-contract/interacting-with-smart-contracts
## **Use Seitrace to Read and Write to Smart Contracts**
Once a contract is verified, its methods are exposed, and direct interaction is possible through Seitrace.
## **Read contract**
Read actions allow you to check various contract attributes. Connecting a web3 wallet is required to make a query, but queries do not require a transaction or any gas costs.
1. **Find the contract address**:
* Locate and enter the contract address you want to interact with into the search bar on Seitrace.
2. **Navigate to the contract page**:
* Select the first option in the search results, which takes you to the token page.
* For more detailed information, click through to the contract page.
3. **Verify contract code**:
* Scroll down past the contract details to see if the code is verified (indicated by a checkmark ✅).
* If the code is not verified, you cannot read or write to the contract unless a verified contract with the same bytecode is found in the Seitrace database.
4. **Proxy Implementation**:
* If the contract is a proxy implementation, you will see options to read/write to the contract or the proxy. A proxy means the contract is upgradeable, and the admin can set a new proxy address for the primary contract if upgrades are needed.
5. **Interact with Contract Methods**:
* Various methods within the contract are visible. Some show current values, while others are queryable.
* For example, to query the `balanceOf` method:
* Fill out the `_owner` (address) field.
* Click on "Query".
* Seitrace will execute the query and return the result under the function.
## **Write Contract**
To write to a contract, follow similar steps as above but with the additional requirement of paying gas fees for transactions:
1. **Find and navigate to the contract**:
* Enter the contract address in the search bar.
* Click through to the contract page from the search results.
2. **Verify contract code**:
* Ensure the contract code is verified.
3. **Proxy Implementation**:
* If applicable, decide whether to interact with the contract or the proxy.
4. **Interact with contract methods**:
* Connect your wallet with MetaMask.
* Fill out the necessary fields for the method you wish to write to. (example on function \_safeMint)
* Click on "Write" and confirm the transaction in your wallet (Metamask).
* The transaction will be sent to the blockchain, and you will receive a transaction hash once completed.
# Seitrace UI
Source: https://docs.seitrace.com/verify-contract/seitrace-ui
Verification is available for both Solidity and Vyper contracts.
Currently, there are 6 methods for verification using the Seitrace UI.
Access function at: [https://seitrace.com/contract-verification](https://seitrace.com/contract-verification)
## **Smart Contract Verification with Seitrace**
1. Go to the Verify contract page *(Resources -> Verify contract(EVM))*
2. Enter in the contract address you received during deployment. The dropdown will show you several available verification options. Select the one you would like to use and continue.
* Solidity (Flattened source code)
* Solidity (Standard JSON input)
* Solidity (Multi-part files)
* Vyper (Contract)
* Vyper (Multi-part files)
* Vyper (Standard JSON input)
### **Solidity (Flattened source code)**
1. **Contract Address:** The `0x` address supplied on contract creation (added above)
2. **Is Yul contract:** Select if the contract is coded in Yul for efficiency.
3. **Include Nightly Builds**: Select if you want to show nightly builds.
4. **Compiler:** derived from the first line in the contract `pragma solidity X.X.X`. Use the corresponding compiler version rather than the nightly build.
5. \*\*EVM Version: \*\*Select the correct[ EVM version ](https://docs.blockscout.com/for-developers/evm-version-information)if known, otherwise use default.
6. **Optimization Enabled:** If you enabled optimization during compilation, select and enter the run value. 200 is the Solidity Compiler default value. Only change if you changed this value while compiling.
7. **Enter the Solidity Contract Code:** You may need to flatten your solidity code if it utilizes a library or inherits dependencies from another contract. We recommend [hardhat ](https://hardhat.org/hardhat-runner/docs/advanced/flattening)or the [POA solidity flattener](https://github.com/poanetwork/solidity-flattener).
8. **Add Contract Libraries:** Enter the name and 0x address for any required libraries called in the .sol file. You can add multiple contracts with the "+" button.
9. Click the `Verify and Publish` button.
10. If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called `Read Contract`. The contract name will now appear in Seitrace with any transactions related to your contract.
### **Solidity (Standard JSON input)**
[More information on JSON input is available here](https://docs.soliditylang.org/en/latest/using-the-compiler.html#input-description)
1. **Include nightly builds**. You can choose **Yes** or **No** depending on your compiler.
2. **Compiler.** Choose the compiler version used to compile your smart contract. If you selected yes for nightly builds, use the compiler version rather than the build.
3. **Standard Input JSON.** Upload your Standard Input JSON file. File should follows solidity [format](https://docs.soliditylang.org/en/latest/using-the-compiler.html#input-description) and all the sources must be in Literal Content format, not a URL.
Click the **Verify & publish** button and wait for the response.
### **Vyper Contract**
1. **Contract Name:** Name assigned to the contract.
2. **Compiler**: Select the compiler version used in the source code.
3. \*\*EVM Version: \*\*Select the correct[ EVM version ](https://docs.blockscout.com/for-developers/evm-version-information)if known, otherwise use default.
4. **Contract Code:** Copy and paste the contract code
5. Click the `Verify and Publish` button.
If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called `Read Contract`. The contract name will now appear in BlockScout with any transactions related to your contract.
### **Vyper Multi-part files and standard json input**
See the information above.
## **Troubleshooting**
If you receive the dreaded `There was an error compiling your contract` message this means the bytecode doesn't match the supplied sourcecode. Unfortunately, there are many reasons this may be the case. Here are a few things to try:
1. Double check the compiler version is correct.
Check all version digits - for example 0.5.1 is different from 0.5.10
2. Check that an extra space has not been added to the end of the contract. When pasting in, an extra space may be added. Delete this and attempt to recompile.
3. Copy, paste, and verify your source code in Remix. You may find some exceptions here.
# Verify contract EVM
Source: https://docs.seitrace.com/verify-contract/verify-contract-evm
Verifying your deployed contract using flattened source code, JSON input, Sourcify and more