Look up a transaction
What a result looks like
A real transaction, explained
Sent 6.2 USDC from xdc8c5fb8…f49e to xdcf29f04…f23a, confirmed in block 109,417,363 on 15 Nov 2026, 09:34 UTC. The fee was 0.000666608 XDC.
- Hash
0x1e411caa3f0c72f4475fde5800fcbfde261919a71e3e80026e12a339fdd2442c- Status
- Success
- Block
- 109,417,363
- Time
- Fee
- 0.000666608 XDC
- Method
- transfer(address,uint256)
Token transfers in this transaction
- 6.2 USDC from
xdc8c5fb8dea6b7a3c1c0d11e03c3da22afe824f49etoxdcf29f049144467b3dc55e19205c30c1737942f23a
Read from the XDC chain by our server on 15 Nov 2026, 10:01 UTC. The same transaction on XDCScan.
How the transaction explainer works
A transaction hash is the fingerprint of one transaction. Anybody can look it up, so the explainer needs nothing but the hash: no address, no wallet, no sign-in.
Where the data comes from
Our server asks the public XDC RPC endpoints (the same ones listed on the RPC status page) for the transaction and its receipt, for the block that holds it, and for the name, symbol and decimals of any token it moved. It does not use a private index or a paid data service, and it does not store your lookup beyond keeping the finished result for a while so that the next request is fast.
Status and confirmations
A transaction that has been sent but is not in a block yet is shown as pending, and the page checks again every 15 seconds until it is included or ten minutes pass. Once it is in a block, the receipt says whether it succeeded or failed (reverted). A failed transaction still costs a fee, because the network did the work. Confirmations count the blocks added after the block that holds the transaction; XDC blocks come about every two seconds, so the count grows quickly and the page stops counting at 100.
Token transfers
Tokens on XDC follow the same event standard as ERC-20 tokens (the XDC docs describe XRC-20 as "similar to the ERC20 standard", XDC docs), and NFTs the ERC-721 pattern. The explainer reads the transfer events in the receipt, asks each token contract for its symbol and decimals, and turns the raw number into a readable amount. Anyone can create a token with any name, so the contract address is always shown, and only Circle's USDC contract is labelled as such.
The fee
The fee is the gas the transaction used multiplied by the price per unit of gas it actually paid, both read from the receipt. Since the January 2026 upgrade XDC has an EIP-1559 style base fee (see the burn tracker); this page shows what the sender paid, not how it was split.
The value in US dollars
The dollar figure uses the CoinGecko price point closest to the time of the block, from CoinGecko's historical price endpoint. Recent prices come at five-minute steps; older ones are hourly or daily, and the page says how far the price point is from the block. It is an estimate of what the XDC was worth, not what an exchange paid, and it is shown for XDC only, not for tokens.
Method names
The method of a contract call is the first four bytes of its input data. We match them against a short list of well-known signatures (transfer, approve, multicall and the like). A match tells you the signature, not that the contract does what the name suggests: the contract is not verified here.
The PDF receipt
The receipt is built in your browser from the result on screen, as a one-page PDF with the summary, the details, a QR code for the transaction on XDCScan and a note that it is a summary of public data, not an official record. Nothing is uploaded.
What the explainer does not show
A summary is only as complete as the receipt. Read these limits before you rely on a result.
Value moved inside a contract call
When a contract sends XDC to somebody as part of a call (an internal transfer, for example the payout of a swap), that movement is not in the receipt. The explainer says so when it finds a contract call with no token transfer; open the transaction on XDCScan to see internal transfers.
Swaps, approvals and other events
Only transfer events are decoded. Other events are counted but not explained, so a swap shows the tokens that moved, not the price or the pool.
Only XDC mainnet
The tool reads XDC Mainnet (chain ID 50). A hash from the Apothem testnet, from Ethereum or from another chain is reported as not found.
Your hash is public, a key is not
A transaction hash is public by design. A private key also has 64 characters but is a secret: never paste one on any website. A secret that has been typed into a page should be treated as exposed.
XDC transaction lookup FAQ
Paste the transaction hash (0x followed by 64 characters) into the box above. The explainer shows whether it succeeded, who sent what to whom, the fee, the confirmations and the value in US dollars at the time of the block.
In your wallet's activity list, in the confirmation screen or email of an exchange withdrawal, or on XDCScan by opening your address. It starts with 0x and has 66 characters in total.
The network has seen the transaction but no block contains it yet. It usually changes within a few seconds on XDC. A transaction that stays pending for long may have too low a fee or a nonce problem in the sender's wallet.
A failed (reverted) transaction was included in a block but the contract rejected the call, so no transfer happened. The fee is still charged. The reason is not in the receipt; the contract's own interface or XDCScan may show it.
There is no single number. XDC makes a block about every two seconds, so a transaction is usually buried under many blocks within a minute. This page shows the count and stops at 100.
The gas used multiplied by the price per unit of gas that the sender paid, shown in XDC and, when the price is available, in dollars at the time of the block.
Yes. After a lookup, choose Download PDF receipt. The file is built in your browser and holds the summary, the details and a QR code for the transaction on XDCScan. It is a summary of public data, not an official record.
From the CoinGecko price point closest to the block's time. The page shows the price, its time and how far it is from the block. It is an estimate, not what an exchange paid.
Either it sent plain XDC, or it called a contract in a way that moves value inside the contract (an internal transfer), which is not in the receipt. Open the transaction on XDCScan for internal transfers.
Yes, a hash is public. Never paste a seed phrase or a private key: a private key also has 64 characters but must stay secret.
No. It reads XDC Mainnet (chain ID 50) only.