Answers to common questions about using the OpenScan.AI explorer at xdcscan.io. If you have a question that isn’t answered here, please reach out via the contact form.
What does the “in” or “out” label mean on a transaction?
This label appears next to a transaction to signify whether a transaction was sent or received by a particular address.
- In: A transaction was sent to the address
- Out: A transaction was initiated from the address
What are the different transaction types?
There are 3 transaction types which can be accessed from the tabs menu for an EOA (Externally Owned Address) or Smart Contract. See Transaction Types for the full breakdown.
Transactions:
An EOA, commonly known as a wallet address, initiates a transaction. Both incoming and outgoing transactions are recorded here, and include any transaction that requires a gas fee (in the native token — XDC on the XDC Network) for execution.
Token Transfers:
Transactions of ERC-20 or ERC-721 tokens. This can include DeFi transactions (like adding or removing liquidity), EOA transfers, airdrops or other transactions where non-native tokens are sent and received.
Internal Transactions:
Transactions initiated and executed between smart contracts. Internal transactions are the result of an external transaction (EOA to contract). This initial transaction can then trigger many internal transactions between contracts as functions are called.
What is CSV export error 504?
If you request too much data at the same time you may receive a timeout. Decreasing the period of time for an export (1 week timeframe is recommended for addresses with lots of transactions) can reduce these errors. See CSV Exports for details.
Can I access and read/write contract methods?
Yes! The contract should be verified (or the bytecode matches an existing verified contract) to enable reading and writing to contracts and proxy contracts. See Interacting with Smart Contracts for more info.
How do I verify a smart contract?
There are multiple methods, including options from the OpenScan.AI UI as well as direct integrations with Hardhat, Foundry, Remix, and Sourcify. See the Contract Verification section:
Which networks does OpenScan.AI operate explorers for?
OpenScan.AI operates xdcscan.io for the XDC Network (chainId 50), with additional instances for EVS, Wanchain, and Velas. Through Explorer-as-a-Service, any project can run its own branded explorer on the same stack — reach out via the contact form to discuss a deployment.
Is there an API I can use?
Yes. Every OpenScan.AI instance exposes a Blockscout-compatible REST API v2 as well as ETH-compatible JSON-RPC endpoints. On XDCScan the API base URL is https://xdcscan.io/api/v2, with interactive documentation at xdcscan.io/api-docs. See APIs for an overview.