Reading a transaction page
A transaction is one thing that happened on the chain: coins moved, a token was sent, or a contract did something. Every transaction has its own page, and it is the page to open when you want to know whether something worked.
Did it go through?
Look at the badge at the top.
Success means the transaction did what it was asked to do. The chain has recorded it and it cannot be reversed by anyone.
Failed means it did not. Nothing moved, and whatever the transaction was meant to do did not happen. One thing does change though: the fee is still charged, because the network did the work of trying. When a transaction fails the page usually shows a revert reason, a short technical note about why. It is not always readable, and you can pass it on to whoever you were transacting with.
A transaction only gets a page of its own once it is in a block. Until then it is waiting in the queue, and it is counted as a pending transaction on the transactions overview but has nothing to show yet.
The main details
| Field | What it means |
|---|---|
| From | The address that sent it and paid the fee |
| To | The address that received it, or the contract it called |
| Value | How much L2P moved. Often 0, because plenty of transactions do something other than move coins |
| Transaction fee | What the sender paid the network to process it |
| Block | The block this transaction was recorded in |
| Confirmations | How many blocks have been produced since. The more there are, the more settled it is |
| Timestamp | When it happened. Hover it to switch between your local time and UTC |
Finalized
Near the top you may see a Finalized badge. It means the block containing this transaction has been agreed on for good and can no longer change, whatever happens next on the network.
A transaction that succeeded but is not yet finalized is almost certainly fine. Finalization is simply the point at which "almost certainly" becomes "definitely". For a large amount, it is worth waiting for.
What kind of transaction it was
Small badges say whether this was a coin transfer, a token transfer or a contract call. Under Method you may see the name of what was called, such as transfer or approve. If the explorer cannot work out the name it shows a short code instead.
The three tabs at the bottom
Token transfers lists tokens that moved while this transaction ran. If someone sent you a token rather than L2P, this is where it shows up, and the Value field above it will be 0. That is normal.
Event logs are the notes contracts leave behind about what they did. Useful to developers, safely ignored by everyone else.
Internal transactions are movements that contracts made as a knock-on effect of this transaction. They are real movements of value, but they are not separate transactions of their own, which is why they are listed here instead.
More details
Behind More details sit the technical fields: position in the block, gas limit, gas price, nonce, transaction type and the raw input data. You never need them for everyday use. They exist so that a developer, or a support person you have asked for help, can see exactly what was sent.
The transaction is not found
Two possibilities. Either the hash is wrong or incomplete, so copy it again in one piece, or it is very new and the explorer has not caught up. Wait a moment and reload.
If it stays missing for a long time, the transaction may never have been sent at all. Check in the wallet you sent it from.
Sharing it as proof
The address of this page is a permanent link to what happened. Sending someone that link is a straightforward way to show that you paid, and it reveals nothing more than the transaction itself, which was already public.