You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The memo is always shown as Base64 encoded, but there is an option to display it as Hex encoded.
For my use case it would be most helpful if I could link to the transaction, passing perhaps a URL query string param, that would default to showing the Hex encoded version, with the option to switch to Base64.
e.g. here it is with hexMemo query string param added.
On a transaction page that has a memo field, for example,
https://stellar.expert/explorer/testnet/tx/2f6da192e5e3b0741695a588dbe4f41a46a5ec93ec2fb1d5aec6a86024553fc7
The memo is always shown as Base64 encoded, but there is an option to display it as Hex encoded.
For my use case it would be most helpful if I could link to the transaction, passing perhaps a URL query string param, that would default to showing the Hex encoded version, with the option to switch to Base64.
e.g. here it is with
hexMemo
query string param added.https://stellar.expert/explorer/testnet/tx/2f6da192e5e3b0741695a588dbe4f41a46a5ec93ec2fb1d5aec6a86024553fc7?hexMemo=true
Thanks for considering.
The text was updated successfully, but these errors were encountered: