The History tab on a Name page shows a full on-chain log of what's happened — registrations, renewals, transfers, resolver changes, record updates, subname creations. This article walks through the columns, the event detail sheet, and the Decoded / Encoded toggle that lets you inspect call data.

On any Name page, click History in the sidebar (last item). The heading is count-led ({N} Transactions, title-cased). The main column renders a filter bar, a list of transaction rows with per-row events folded under them, and a search input (Search…). The tab currently reflects Sepolia activity only.

Table columns: Date ⇅ / Transaction ⇅ / From ⇅ / Network ⇅. Each row has an expand chevron with a count badge (1, 3, depending on how many events the transaction contains), a date, an orange Tx-hash pill, a From cell (avatar + green pill when the sender is the owner), a Sepolia network glyph, and a trailing More button. Clicking the chevron expands child rows — one per event — with only the event name in the Transaction column. Clicking More opens a right-hand Transaction slide-out sheet with the full detail.

Sheet title: Transaction. Rows: Name, Tx Hash, Timestamp, Network, From, To. Below the top rows, an H2 like 3 events heads a list of per-event panels. Each event panel has the event name + a copy icon, a top-right Go to docs outline button that takes you to the documentation for that event, rows for Transaction (Tx hash) and Event (Solidity signature, e.g. ResolverUpdated (uint256 tokenId, address resolver)), and a Data heading with the Decoded/Encoded toggle. Observed event names include SubregistryUpdated, NameRenewed, ResolverUpdated, Transfer, LabelRegistered. Each panel is independent — expand one, read its data, collapse and move to the next.

Every on-chain event carries a payload of typed parameters, and the Data section on each event panel has a binary switch in the top-right labelled Decoded when on and Encoded when off. There is no third "RAW" mode — the split is two-way, and the underlying event is the same; you're just choosing the lens.

In Decoded mode the panel shows a table with columns #, Name, Type, Data, so you can read each parameter of the Solidity event in human terms. In Encoded mode the panel shows the raw ABI-encoded payload that went on-chain — useful when you need to reproduce, diff, or feed bytes into another tool (a simulator like Tenderly, a bytes-equal check against another transaction, or a custom decoder). A Copy icon on the event header copies the event signature; per-parameter copy lives inside the decoded table rows.

The filter bar has two dropdowns: Date: All ˅ and Event: All ˅ (no Network filter). A Search… input next to them lets you narrow by keyword, hash, or address. An ↕ Expand all button toggles to ↕ Collapse all to show or hide all child events at once. Per-row, the hash pill is the link — clicking the transaction hash jumps to the transaction on Sepolia Etherscan for the full chain-level picture (gas, internal transactions, logs, events). Etherscan is the source of truth at the chain level; Explorer's History tabs are curated, ENS-aware views on top.

Why does the Encoded view say "data not available"?

If the raw payload isn't present, the Encoded view shows the fallback copy Encoded data not available. Transaction receipt may still be loading. This reads like a permanent error but is usually transient — the Explorer backend is still fetching the receipt from the indexer. Wait a few seconds and toggle off-and-on again. If the fallback persists on a transaction that's been final for a while, reload the page to clear it.

Which view should I use for debugging?

Start with Decoded — it tells you which event fired with which arguments, which is usually enough. If something looks off — an unexpected parameter, a transaction that looks like it should have done one thing but did another — switch to Encoded and paste the bytes into your own decoder or a simulator. For chain-level detail, click the transaction hash to open it on Sepolia Etherscan.

Why is a transaction missing from this tab?

The name-page History (/<name>.eth/history) and the address-page History (/addr/<address>/history) use different event filters with no documented difference. The address page may include events the name page omits and vice versa — neither is a complete log on its own. If a transaction is missing from one tab, check the other before assuming it did not happen.