Author

Topic: Can someone explain this transaction? (Read 310 times)

hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
March 14, 2018, 09:04:35 PM
#9
That's the Raw transaction in HEX format.
To Decode Hex format to "human readable" format, use: https://blockchain.info/decode-tx
---snip---

0.0995BTC was sent to 3BLhSgpY9xCFJv9Y6AyA9eSRZT6k3z6w4s bitcoin address.
Transaction ID: 91c8b08f305d895d6bc8f43bbdd36dcbc7f1d998e3df5e8f13dd9cdeebf15cb5
this right. how do you know about that ?
how do you search in such detail like that ?
can you give a complete tutorial of the process ?

He clearly stated in his post how to do (decode) that
and to the OP if you extracted the actual rawtx, it would give you this
https://blockchain.info/rawtx/91c8b08f305d895d6bc8f43bbdd36dcbc7f1d998e3df5e8f13dd9cdeebf15cb5?format=hex
the rawtx you posted is just an unsigned rawtx version, easily created if you understand the basic of transaction format
sr. member
Activity: 686
Merit: 262
Enterapp Pre-Sale Live
March 14, 2018, 06:56:19 PM
#8
That's the Raw transaction in HEX format.
To Decode Hex format to "human readable" format, use: https://blockchain.info/decode-tx
Code:
{
   "lock_time":0,
   "size":85,
   "inputs":[
      {
         "prev_out":{
            "index":1,
            "hash":"224d4b8a7f0b11860019a6fd3fa51794855ef5ea7c36d7907a909ecda16205a3"
         },
         "script":"0151"
      }
   ],
   "version":1,
   "vin_sz":1,
   "hash":"91c8b08f305d895d6bc8f43bbdd36dcbc7f1d998e3df5e8f13dd9cdeebf15cb5",
   "vout_sz":1,
   "out":[
      {
         "script_string":"OP_HASH160 69d98314fbc4dbee037f86f51392a14c4c1d41da OP_EQUAL",
         "address":"3BLhSgpY9xCFJv9Y6AyA9eSRZT6k3z6w4s",
         "value":9950000,
         "script":"a91469d98314fbc4dbee037f86f51392a14c4c1d41da87"
      }
   ]
}
0.0995BTC was sent to 3BLhSgpY9xCFJv9Y6AyA9eSRZT6k3z6w4s bitcoin address.
Transaction ID: 91c8b08f305d895d6bc8f43bbdd36dcbc7f1d998e3df5e8f13dd9cdeebf15cb5
this right. how do you know about that ?
how do you search in such detail like that ?
can you give a complete tutorial of the process ?
newbie
Activity: 4
Merit: 0
March 14, 2018, 11:40:28 AM
#7
you posted similar thing on another thread https://bitcointalksearch.org/topic/help-with-transaction-3120917
did you find this rawtx somewhere? or you picked some random address, create unsigned rawtx and ask questions here
what exactly you are trying to achieve? Roll Eyes I'm pretty sure those aren't your addresses

I found it in a an article talking about strange inputs.
HCP
legendary
Activity: 2086
Merit: 4361
March 14, 2018, 09:51:35 AM
#6
I suspect someone was just messing about... The "script" decoded as:
PUSHDATA(1)[51]... So it pushes 1 byte onto the stack... And that byte is [51]

[51] resolves to OP_TRUE.

So, it's an "Anyone-Can-Spend" output:
Anyone-Can-Spend Outputs
Conversely a transaction can be made spendable by anyone at all:

 scriptPubKey: (empty)
 scriptSig: OP_TRUE
With some software changes such transactions can be used as a way to donate funds to miners in addition to transaction fees: any miner who mines such a transaction can also include an additional one after it sending the funds to an address they control. This mechanism may be used in the future for fidelity bonds to sacrifice funds in a provable way.

Anyone-Can-Spend outputs are currently considered non-standard, and are not relayed on the P2P network.
legendary
Activity: 3038
Merit: 4418
Crypto Swap Exchange
March 14, 2018, 09:45:29 AM
#5
Yes, it is certainly a strange transaction. The reason the scriptsig is weird and small is because it doesn't contain any signatures. It's a special case since transactions without any signatures shouldn't be accepted. The scriptsig has to return true for the transaction to be considered valid and in most cases, the condition (ie. transaction is signed by n-of-m parties for multisig) has to be met.

Take the transaction and decode it.
Code:
"script":"0151"

You will notice that the script line is "0151". The redeem script for that address is basically the number 51. It's the hex for OP_True and it is thus valid without the need for a signature.
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
March 14, 2018, 04:33:32 AM
#4
you posted similar thing on another thread https://bitcointalksearch.org/topic/help-with-transaction-3120917
did you find this rawtx somewhere? or you picked some random address, create unsigned rawtx and ask questions here
what exactly you are trying to achieve? Roll Eyes I'm pretty sure those aren't your addresses
legendary
Activity: 1042
Merit: 2805
Bitcoin and C♯ Enthusiast
March 14, 2018, 04:16:14 AM
#3
...

Dude, the problem is not with decoding the tx. The problem is that the ScriptSig of this transaction is too short!
Commenting here so I can follow!
legendary
Activity: 2534
Merit: 6080
Self-proclaimed Genius
March 14, 2018, 02:34:29 AM
#2
That's the Raw transaction in HEX format.
To Decode Hex format to "human readable" format, use: https://blockchain.info/decode-tx
Code:
{
   "lock_time":0,
   "size":85,
   "inputs":[
      {
         "prev_out":{
            "index":1,
            "hash":"224d4b8a7f0b11860019a6fd3fa51794855ef5ea7c36d7907a909ecda16205a3"
         },
         "script":"0151"
      }
   ],
   "version":1,
   "vin_sz":1,
   "hash":"91c8b08f305d895d6bc8f43bbdd36dcbc7f1d998e3df5e8f13dd9cdeebf15cb5",
   "vout_sz":1,
   "out":[
      {
         "script_string":"OP_HASH160 69d98314fbc4dbee037f86f51392a14c4c1d41da OP_EQUAL",
         "address":"3BLhSgpY9xCFJv9Y6AyA9eSRZT6k3z6w4s",
         "value":9950000,
         "script":"a91469d98314fbc4dbee037f86f51392a14c4c1d41da87"
      }
   ]
}
0.0995BTC was sent to 3BLhSgpY9xCFJv9Y6AyA9eSRZT6k3z6w4s bitcoin address.
Transaction ID: 91c8b08f305d895d6bc8f43bbdd36dcbc7f1d998e3df5e8f13dd9cdeebf15cb5
newbie
Activity: 4
Merit: 0
March 14, 2018, 01:17:16 AM
#1
I decoded this transaction but the scriptsig was weird. Can someone explain what is happening with it and how to create one like it.

Raw transaction:
0100000001a30562a1cd9e907a90d7367ceaf55e859417a53ffda6190086110b7f8a4b4d2201000 000020151ffffffff0130d397000000000017a91469d98314fbc4dbee037f86f51392a14c4c1d41 da8700000000
Jump to: