Skip to main content

.What's on the History tab in ENS Explorer?

How to read the History tab in ENS Explorer — event rows, the Transaction detail sheet, and the binary Decoded/Encoded toggle on each event.

Note: The ENS App and ENS Explorer are both currently on Sepolia testnet. Behaviour and available features may change before mainnet.

The History tab on a Name page in ENS Explorer lists everything that has happened to the name onchain. That includes registrations, renewals, transfers, resolver changes, record updates and subname creations. To open it, select History in the sidebar of any Name page.

Read a transaction row

Each row in the list is one transaction, showing its date, transaction hash, sender and network. Expand a row to see the individual events inside it. Select More to open the Transaction sheet, which shows the full detail plus a panel for each event. Each panel shows the event signature, a Go to docs button for that event's documentation, and a Data section.

Decoded and encoded data

Each event's Data section has a toggle with two views of the same event. Decoded shows each parameter in a table: name, type and value. Encoded shows the raw payload as it went onchain. Use it when you need the bytes, for example for a decoder or a simulator.

Filter the list and open Etherscan

Use the Date and Event filters or the search box to narrow the list. Expand all opens every row's events at once; select it again to collapse them. Select a transaction hash to open it on Sepolia Etherscan for chain-level detail such as gas and logs.


Common questions

Why does the Encoded view say data is not available?

When the Encoded view says the data is not available, the transaction receipt is usually still loading. Switch the toggle off and on again. If the message stays on a transaction that has already confirmed, reload the page.

Which view should I use for debugging?

For debugging, start with the Decoded view: it shows which event fired and with which arguments. If a value looks wrong, switch to Encoded and paste the bytes into your own decoder or simulator. For chain-level detail, open the transaction on Etherscan instead.

Did this answer your question?