[member=31975]saeveritt[/member] asked in the chat why his OP_RETURN message has an L in front of his text: https://chainz.cryptoid.info/ppc/tx.dws?1026201.htm
The short answer is: It’s a bug on the cryptoid website.
The long answer:
Let’s have a look at the json version of the txn output:
"asm": "OP_RETURN 5468616e6b20796f7520666f7220796f757220776f726b20616e642064656469636174696f6e2c20706565726368656d6973742e20596f757220667269656e642c207361657665726974742e",
scriptPubKey holds the full script of the transaction output, this is the smart contract code and an OP_RETURN output is a specific form of smart contract. (Read more here: https://en.bitcoin.it/wiki/Script)
You see both the asm and hex representation. If you decode the hex data in the asm representation (everyting coming after “OP_RETURN”), you get:
Thank you for your work and dedication, peerchemist. Your friend, saeveritt.
You get exactly what [member=31975]saeveritt[/member] has posted.
However, if you decode the hex representation, you get:
jLLThank you for your work and dedication, peerchemist. Your friend, saeveritt.
You can see three bytes added to the front: “6a 4c 4c”
The hex represention contains the full script and these three bytes are:
4c: 76 -> the length of the OP_RETURN message: you can PUSH up to 75 bytes with a single OP code, and pushing 76-78 bytes requires OP_PUSHDATA1 <len> <data>
4c is also the utf-8 code for “L” and the cryptoid page fails to identify the third byte as not being part of the message data and therefore adds it to the front of the message.