Anything that writes to the chain (saving records, changing a resolver, granting roles, deploying a subregistry, creating a subname) opens the Transaction Manager over the page. It lists the steps, estimates the gas, and walks you through signing.

Not started. Each step shows its estimated gas. Nothing has been sent. Select Start to begin, or close the dialog to walk away at no cost.

Waiting. The transaction is with your wallet. Sign to continue, reject to cancel. A progress bar fills while the network receives and confirms it. On a slow network this can sit for a while.

Confirmed. The step turns to a tick with a link out to Etherscan. On the last step the button becomes Done.

Rejected. You turned it down in your wallet. Nothing was sent and you paid nothing. Try again restarts the flow.

Some actions have more than one step, each with its own wallet prompt. Deploying a subregistry (the contract that manages a name's subnames) asks you to deploy it, then to set it on your name. Deploying a new permissioned resolver asks you to deploy it, then to point your name at it. After the first step confirms, the button changes to Next; select it to send the second. Rejecting either step stops the flow there; anything already confirmed stays done.

Explorer is catching up with the chain. Your change has already landed. If a value still reads the old state a minute later, refresh the page.

No. A rejected transaction never reaches the chain, so there's no gas to pay.

Yes. Steps that already confirmed stay confirmed. Reopen the action to finish the rest.