Transaction History Web3 Block for React

Both replace the pending transaction with a new one at the same nonce, which a chain only accepts if the fee is higher. Speed up raises the gas price by at least 10 percent, rounded up to a whole gwei, and shows the old and the new fee; the row reads Replaced with a higher fee. Cancel sends nothing to anyone: it is a zero-value replacement, and the row reads Cancelled. Undo puts the demo back.

A wallet's own transactions run in nonce order. While nonce 43 is pending, nothing after it can be confirmed, so a stuck transfer blocks the next one you send. The note under the pending row says this, and replacing or cancelling is the way to unblock it.

Gas used times the gas price in gwei, divided by a billion, in ether, with a rough dollar figure from a typed sample rate. For a pending transaction the figure uses the gas limit. Received money shows Paid by the sender, because the sender pays the fee.

All of it. The transactions, hashes and addresses are typed and invented, and Speed up and Cancel only change local state; the message says nothing was sent to a chain. In your app read history from your indexer, send the replacement through the user's wallet with the same nonce, and let the wallet sign it.

Yes. The list sits in a named, focusable scroll region of fixed height, so any filter changes the rows and not the panel. With no match an empty state in the same space offers Show all transactions, and the polite status line says how many of the fourteen show.

The chips become a four-column grid, the type select spans the width, and each row keeps its tile, a title with the counterparty under it, and the amount with the status at the end. Day headings stay pinned while their rows scroll.