Copy transaction ID button

[nubeasado]

Problem

Trying to copy transaction IDs from an account's 'recent operations' section is painful. Currently it requires highlighting the transaction ID, then while still depressing the left mouse button, hitting ctrl+c / cmd+c.
After copying you then have to highlight half the page to avoid being sent to the specific transactions page, if you do go to the transaction specific page it takes 15+ seconds to go back to the recent operations page exactly where you were.

The last point is incredibly frustrating if you're looking through a lot transactions.

Solution

A copy button.

EtherScan example - https://etherscan.io/address/0x4838b106fce9647bdf1e7877bf73ce8b0bad5f97

Alternatives

No response

[svienot]

When you navigate from the recent operations table to the transaction details, if you then click the browser's back button, it should bring you back to the exact same page of that table. Isn't this what you observe?

Also, to make sure I fully understand your workflow, where exactly do you need to paste the TransactionID after copying it?

[nubeasado]

When you navigate from the recent operations table to the transaction details, if you then click the browser's back button, it should bring you back to the exact same page of that table. Isn't this what you observe?

In theory this is how it works and is nice; in practice however it can be quite clunky.
For example:
A user contacts us thinking they've lost crypto, they're not quite sure what they've done and can't understand their transaction history. As i'm going through their transaction history, I click on each transaction to copy the transaction ID to send to them in a more readable format. Sometimes there may be 50+ transactions of interest, so i'll have to click into each transaction one by one, copy the transaction id, go back, scroll down to where I was and continue.

That's an issue because I now have to take a few seconds to figure out exactly how far down the page I was, has the page updated as new transactions came through etc.? Doing this once annoying but fine, however if you're doing this multiple times per day or per week it becomes quite frustrating.

Also, to make sure I fully understand your workflow, where exactly do you need to paste the TransactionID after copying it?

Anywhere else e.g. email, slack, google doc, discord, reddit etc.
In the example above, it would be in a support message I can send to the user of their transaction history in a slightly more readable format, e.g.
Swap 250 HBAR to 1084 SAUCE
0.0.7676946@1739302842.668000000

This also leads onto another issue which is mostly covered by #1598, surrounding transactions not being grouped, but that's a separate pain point.

[svienot]

Thank you for providing this background information.

Are you aware you have the ability to download the account transactions in a CSV file?
This might be more convenient for you to obtain the list of transaction IDs you want to send to your user.

Just in case, here is the download button (brings up a dialog allowing to select the kind and range of transactions to download):

[nubeasado]

I am aware of the CSV download, however i don't find it very useful as there doesn't appear to be a way to download every transaction type. You have to choose which specific types of transactions you want. If you want everything, you need to download multiple, then manually stitch them together

[svienot]

To download all types at once, you can select TYPES: ALL in the download dialog (like in the interactive view selector):

[nubeasado]

nice, that's useful if i wanted to download a CSV.

Regardless, having a copy transaction ID button would still be extremely helpful 🙌

[svienot]

This is still a valid enhancement. The issue is that our current table design is such that one click (anywhere) in a row navigates to the details of the corresponding entity. We'll need to change that to have individual actions attached to the click on various cells in a row. When this is done, it will have to be done on all the tables of the explorer, to be consistent, so this is a substantial task which we just have not had the possibility to tackle so far.