bitcoin core – Transaction status: 0 / not confirmed, not in mempool

The software Bitcoin Core is using?

Then you need to have your software forget about your unconfirmed transaction that is not in the mempool, so you can do it again at a higher fee.

When starting your Bitcoin Core, run it with -zapwallettxes. This will make your wallet forget about the unconfirmed transactions relevant to your wallet. You can learn how to add that on Andrew Chow's blog.

Then the balance in your wallet must be converted to the balance before making the payment.

I learned this from here, but the other two methods are not applicable as you need to change your transaction to increase the fee.

raw transaction – Blockcypher make_tx_signatures "Bad Signature" error

I am having trouble signing a transaction on the Blockcypher Test Network (using python):

import requests
from blockcypher (
    import send_faucet_coins, create_unsigned_tx, 
    make_tx_signatures, broadcast_signed_transaction
)

1. Create two new addresses

url = 'https://api.blockcypher.com/v1/bcy/test'
address_input = requests.post('%s/%s' % (url, 'addrs'), json={'token': api_key}).json()
'''
{'address': 'C45nBYCjNx1f9YVvSoXrS9uj21cJZCqdRP',
 'private': 'dde71ff0e59daa55ab9db6fc99b0c060d1d2b7948aa4fece27b876696e7a369d',
 'public': '027a4e91b0720d8820c78408ac7f3278b447efa03c5c21342d7086efacc0c43536',
 'wif': 'BvmP3YKzHW8BVaJ3RjrVh6zCDg9DhCHP4LqYVX6s3HxvPUpnSSUF'}
'''

address_output = requests.post('%s%s' % (url, 'addrs'), json={'token': api_key}).json()
'''
{'address': 'BtfkLhMMSJunX3CA43BAE1zmGnruabeDxs',
 'private': 'f4250bf0f077d11c38813ff6353f2d6750e24f3bc52b371760a397663069f31a',
 'public': '0245f4be87a2bd036abae729da25db58e2cfed964fdd385874aa71595c30c1339e',
 'wif': 'BwWch8gMhu37j9d73JMN7Gj5FvDjkpMGseyLnuxmGe4SKByR8Ljc'}
'''

2. Send some tap coins to the address of entry

send_faucet_coins(
    address_to_fund=address_input('address'), 
    satoshis=100000000, 
    coin_symbol='bcy', 
    api_key=api_key)
'''
{u'tx_ref': u'0de7b2b73de2d8b6588202b129ea96dfe1890adcd7fb174f75398b4ed1dd0728'}
'''

3. Create an unsigned transaction

inputs = ({'address': address_input('address')}, )
outputs = ({'address': address_output('address'), 'value': 900000})
unsigned_tx = create_unsigned_tx(
    inputs=inputs, 
    outputs=outputs, 
    coin_symbol='bcy', 
    include_tosigntx=True, verify_tosigntx=True,
    api_key=api_key)
'''
{'tosign': ('7f7f02da6565f3409fef83cad257324e9fe3f4e85444d8afafa5521d7dea6570'),
 'tx': {'addresses': ('C45nBYCjNx1f9YVvSoXrS9uj21cJZCqdRP','BtfkLhMMSJunX3CA43BAE1zmGnruabeDxs'),
 'hash': '275ddde93ee1b85ce5583a09c4d69667a546df3dd4dc79623690857d6594e580',
  'inputs': ({'addresses': ('C45nBYCjNx1f9YVvSoXrS9uj21cJZCqdRP'),
     ...}),
  'outputs': ({u'addresses': (u'BtfkLhMMSJunX3CA43BAE1zmGnruabeDxs'),
    ...
    'value': 900000},
   ...),
  ...}}
'''

Then I have to sign the unsigned transaction and where the error stops:

###4. Sign the unsigned transaction###

tx_signatures = make_tx_signatures(
    txs_to_sign=unsigned_tx('tosign'), 
    privkey_list=(address_input('private')), 
    pubkey_list=(address_input('public')))

AssertionError: Bad Signature: sig 30440220588709fa21ea1b9c019e71a74ce1994f10c2c20560f160debf37da8de439942802202841dc452ee04af690e0fba97d304cc98cf84c47f435946197a0c50900c9bda7 for tx 7f7f02da6565f3409fef83cad257324e9fe3f4e85444d8afafa5521d7dea6570 with pubkey 027a4e91b0720d8820c78408ac7f3278b447efa03c5c21342d7086efacc0c43536

I tried to sign the transaction with btcutils / signer, it shows me the same signature, which works perfectly:

signatorytransaction_design) (private key)

./signer 7f7f02da6565f3409fef83cad257324e9fe3f4e85444d8afafa5521d7dea6570 dde71ff0e59daa55ab9db6fc99b0c060d1d2b7948aa4fece27b876696e7a369d

The result of identical signatures:
30440220588709fa21ea1b9c019e71a74ce1994f10c2c20560f160debf37da8de439942802202841dc452ee04af690e0fba97d304cc98cf84c47f435946197a0c50900c9bda7

5. Now you could successfully stream it to Blockcypher Network

tx_signatures = ('30440220588709fa21ea1b9c019e71a74ce1994f10c2c20560f160debf37da8de439942802202841dc452ee04af690e0fba97d304cc98cf84c47f435946197a0c50900c9bda7')
broadcast_signed_transaction(
    unsigned_tx=unsigned_tx, 
    signatures=tx_signatures, 
    pubkeys=(address_input('public')), 
    coin_symbol='bcy', 
    api_key=api_key)
'''
{'tosign': (''),
 'tx': {'addresses': ('C45nBYCjNx1f9YVvSoXrS9uj21cJZCqdRP', 'BtfkLhMMSJunX3CA43BAE1zmGnruabeDxs'),
  'hash': 'b954b6d225d84d77e65f22490b09409cf77d245e82b023181c1dac9f48b8f45d',
  'inputs': ({'addresses': ('C45nBYCjNx1f9YVvSoXrS9uj21cJZCqdRP'),
    ...
    }),
  'outputs': ({'addresses': ('BtfkLhMMSJunX3CA43BAE1zmGnruabeDxs'),
    ...
    'value': 900000},
   ...}),
  ...}}
'''

What is wrong with Blockcypher.make_tx_signatures ?
Could it be a problem to use BCY symbol for Blockcypher TestNetintead's BTC for Bitcoin TestNet?

wallet – Use case for multiple entries in a single transaction

Is there a way to determine if a pair or more of Bitcoin addresses belong to the same wallet on the basis that a pair of addresses was used as input for a single transaction?

No.

Assuming all entries to a transaction are from the same wallet is often referred to as a “ common entry property heuristic & # 39; & # 39 ;, but it is possible to create transactions using entries from multiple wallets, so there is no way to apply this heuristic with 100% accuracy. In many cases it can work, but in many cases it will fail.

Can I verify that the address pair entry is not part of a transaction creation transaction or fund raising transactions, for example from a blockchain browser?

No, the transaction data transmitted to the network deliberately lacks information on what software / method was used to prepare the transaction. In some cases, the & # 39; fingerprint of transactions & # 39; It can be used to make an assumption about this, but again it's just an assumption, at best false positives can easily be created as well.

In which case, in addition to createrawtransaction and fundrawtransaction, multiple entries within a single transaction belong to different wallets?

Some examples:

  • Coin transactions (eg Wasabi wallet, join the market)
  • Lightning Network channels (2of2 multisig)
  • Other multi-grade wallets (many possible situations)
  • Payjoin transactions (similar to coinjoins, though not many afaik job implementations)
  • etc.

Cannot send raw transaction Bitcoin Core 0.19.1 – script verification flag not required (signature must be zero for failed SIG CHECK (MULTI) operation)

I wanted to send a raw testnet transaction and was doing it like in the bitcoin documentation, but I still get this error:

non-mandatory script verification flag (signature must be zero for failed SIG CHECK (MULTI) operation) (code 64) (code -26).

What am I doing wrong?

  1. I take a transaction from me listunspent
{
    "txid": "8ee71fee9e4706100c09fb2da4c3ccdac1a4475981bd893ba1eba9417947abff",
    "vout": 0,
    "address": "2Mw44JvAhBs4hgh5bT3gP2NgbhTbVwngW1m",
    "label": "",
    "redeemScript": "00143b88811e01b3efaa0bcd9da16ef85ef3a1583349",
    "scriptPubKey": "a91429c3d920cd18e34db9035c4322474aae4465792187",
    "amount": 0.02641617,
    "confirmations": 16197,
    "spendable": true,
    "solvable": true,
    "desc": "sh(wpkh((8939dfa5/0'/0'/8')02a44b3dd2f0964048265982156f668c037dfabc140eb98f292dbb723d28b85261))#husuy9tw",
    "safe": true
}
  1. Then I create a raw transaction from this:
createrawtransaction '({"txid":"8ee71fee9e4706100c09fb2da4c3ccdac1a4475981bd893ba1eba9417947abff","vout":0})' '{"2NCH5HXBwfHegFEUTNrkSKzyYTnTYQKDUjU":0.02}'
  1. dumpprivkey

  2. And sign the transaction like this

signrawtransactionwithkey '0200000001ffab477941a9eba13b89bd815947a4c1daccc3a42dfb090c1006479eee1fe78e0000000000ffffffff0180841e000000000017a914d0c3f50336b5f109207d722c692191ff86263e968700000000' '(" $privKey ")' '({"txid":"8ee71fee9e4706100c09fb2da4c3ccdac1a4475981bd893ba1eba9417947abff","vout":0,"scriptPubKey":"a91429c3d920cd18e34db9035c4322474aae4465792187","redeemScript":"00143b88811e01b3efaa0bcd9da16ef85ef3a1583349","amount":0.02})'

{
  "hex": "02000000000101ffab477941a9eba13b89bd815947a4c1daccc3a42dfb090c1006479eee1fe78e00000000171600143b88811e01b3efaa0bcd9da16ef85ef3a1583349ffffffff0180841e000000000017a914d0c3f50336b5f109207d722c692191ff86263e968702473044022010c174b3306cac5ca8ddbb6eadf0de2299c2a216ade25088290c17880aa5bd60022017bc9de608e7ff59ffa09a6a60d848875d37edfc4a4b687f0eb94d4c2cd11b4f012102a44b3dd2f0964048265982156f668c037dfabc140eb98f292dbb723d28b8526100000000",
  "complete": true
}

But when I want to send a raw transaction

sendrawtransaction 02000000000101ffab477941a9eba13b89bd815947a4c1daccc3a42dfb090c1006479eee1fe78e00000000171600143b88811e01b3efaa0bcd9da16ef85ef3a1583349ffffffff0180841e000000000017a914d0c3f50336b5f109207d722c692191ff86263e968702473044022010c174b3306cac5ca8ddbb6eadf0de2299c2a216ade25088290c17880aa5bd60022017bc9de608e7ff59ffa09a6a60d848875d37edfc4a4b687f0eb94d4c2cd11b4f012102a44b3dd2f0964048265982156f668c037dfabc140eb98f292dbb723d28b8526100000000

non-mandatory-script-verify-flag (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 64) (code -26)

I tried a lot of transactions but I can't send it and I can't see what I'm doing wrong. Normally the Bitcoin Core submit button works fine.

segregated token: unable to sign Segwit transaction entry on bitcoinj

I want to spend from a segwit address and it has a P2WPH script, I created this transaction just like creating a normal P2PKH transaction, but just changed the input address to the segwit address, I don't know if this is correct, and sign this transaction with the next method but it says the script was NOT verified correctly …

Transaction signedtx = signInput(rawtx.getHashAsString(),privkey,rawtx);

    public static Transaction signInput(String hash, String prvKey,Transaction spendTx) {
        ECKey ecKey = ECKey.fromPrivate(Utils.HEX.decode(prvKey));
        ECKey.ECDSASignature signature = ecKey.sign(Sha256Hash.wrap(hash));
        TransactionSignature transactionSignature = new TransactionSignature(signature,Transaction.SigHash.ALL,true);
        TransactionWitness witness = TransactionWitness.redeemP2WPKH(transactionSignature,ecKey);
        TransactionInput input = spendTx.getInput(0);
        input.setWitness(witness);
        return spendTx;
    }

I am not very familiar with bitcoinj, and currently there is very little technical guidance related to segwit, I hope someone can help me!

segregated token – get public key of any raw transaction – what to do?

I need to retrieve the public key from the sender of the transaction.

now i know there are 03 compressed pubkeys and 04 uncompressed.

but how does this work with segwit and multigrade addresses?

Could you tell me what possible combinations there could be, so I'm ready for any possible reaction to always get the right key?

Thanks a lot!

How does a blockchain permanently accept a transaction?

If miner A creates a block containing transaction A and miner B creates a block that does NOT contain transaction A at approximately the same time, then some of the other miners will receive block from miner A first and the others will receive block from miner B. (fork)

If Miner's B chain grows faster than Miner's A chain, then Transaction A will never be accepted (as it never happened). So how user A who created transaction A can be sure that transaction A was accepted / verified by blockchain?

Also, is there a chance that transaction A will be verified by the blockchain at some point and then in the future another substring (from a previous fork) that does not contain transaction A will grow faster, thus rejecting transaction A?

Is there a created time control point that all miners should agree on?

Why is the transaction log not really circular (SQL Server)?

I did a little research recently on how the transaction log works on the sql server.
Now I come to a problem, which I cannot understand.

At first, I created a new test database with full recovery mode and created an empty test table in it.
Then I did an initial full backup and then a first tlog backup as well. This resulted in the following DBCC LOGINFO output:

enter the image description here

So far so good. Then I inserted multiple rows, to make sure the first three VLFs are in use. As a next step, I did another tlog backup and a manual checkpoint so that the first two VLFs were truncated, resulting in this DBCC LOGINFO:

enter the image description here

Then I added more rows, so that the transaction log would fit and the database engine would use the first VLF again. On top of that, I added more and more rows and finally the second VLF was full. Because the third VLF was not yet truncated, the transaction log grew and an additional four VLFs were added. After all this, I made the following transaction log backup and also a manual checkpoint, which eventually led to this:

enter the image description here

Now what bothers me is what happened next. I thought when I make so many changes, that the last VLF (here in row 8) will fill up, the record will wrap again and start writing to the first VLF again (here with FSeqNo 41), since this VLF is already truncated Lo I was hoping because at "https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-transaction-log-architecture-and-management-guide?view=sql-server-ver15", they suggest, that the transaction log is circular in nature. But what really happened is that the database engine wrote to the following VLF with the lowest FSeqNo:

enter the image description here

Why is this behavior contrary to Microsoft documents or, what is more likely, I am just dumb and did not understand the ms docu well?
Any help or explanation for a real doll would be appreciated.
I hope to hear from you and thanks in advance for the possible help.

Sincerely,

signature – How do I get hash to verify the transaction?

This is how things can be done backwards. Unfortunately, the bitcoin-explorer (bx) verification mechanism works a little differently but somewhat similar to what I expected. Step 4 below can provide details that may be helpful to what you are doing. Step 5 below completes the offline validation.

1. Here is the easy way to calculate the transaction IDs of the raw hexadecimal transactions.

Echo 01000000018a8a9f938c251be60da2711c6bf168c66213fae8e26251fcec47f9a41d0e71e3020000006b483045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d012103c0f217eb4428c61d47d8aa084a28c3d3d26f43b6569283f08fec5451a5fc8c98ffffffff0200803801000000001976a914d2c6b9c7f146ea4039e6ae67904eb94d479b7ed688ac06d79e460e0000001976a914b85f8cde95fe9b30872e49d5b961a4af5d07518688ac00000000% | bx bitcoin256

9b4912711de5e258a74a529227f43647bc3b2304212fb508c5f8e910d5986270

2. Here are two means (the first is offline, the second is online) to extract the Endorsement / Signature and the associated Public Key used for the TX_ID 9b4912711de5e258a74a529227f43647bc3b2304212fb508c5f8e910d5986270 entry:

Echo 01000000018a8a9f938c251be60da2711c6bf168c66213fae8e26251fcec47f9a41d0e71e3020000006b483045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d012103c0f217eb4428c61d47d8aa084a28c3d3d26f43b6569283f08fec5451a5fc8c98ffffffff0200803801000000001976a914d2c6b9c7f146ea4039e6ae67904eb94d479b7ed688ac06d79e460e0000001976a914b85f8cde95fe9b30872e49d5b961a4af5d07518688ac00000000% | bx tx-decode

or

% bx fetch-tx -c ~ / bitcoin-explorer / bx-mainnet-remote.cfg 9b4912711de5e258a74a529227f43647bc3b2304212fb508c5f8e910d5986270

that both produce:

transaction
{
    hash 9b4912711de5e258a74a529227f43647bc3b2304212fb508c5f8e910d5986270
    inputs
    {
        input
        {
            address_hash a0d48c129cfde8f124a16f4d69bc47fd7fb5780d
            previous_output
            {
                hash e3710e1da4f947ecfc5162e2e8fa1362c668f16b1c71a20de61b258c939f8a8a
                index 2
            }
            script "(3045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d01) (03c0f217eb4428c61d47d8aa084a28c3d3d26f43b6569283f08fec5451a5fc8c98)"
            sequence 4294967295
        }
    }
    lock_time 0
    outputs
    {
        output
        {
            address_hash d2c6b9c7f146ea4039e6ae67904eb94d479b7ed6
            script "dup hash160 (d2c6b9c7f146ea4039e6ae67904eb94d479b7ed6) equalverify checksig"
            value 20480000
        }
        output
        {
            address_hash b85f8cde95fe9b30872e49d5b961a4af5d075186
            script "dup hash160 (b85f8cde95fe9b30872e49d5b961a4af5d075186) equalverify checksig"
            value 61314356998
        }
    }
    version 1
}

Distinguished Encoding Rules (DER) in Signature format = 3045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d01

R =

% echo 3045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f01e674
00ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed429

S =

% echo 3045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f01e6379
4efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d

Pubkey = 03c0f217eb4428c61d47d8aa084a28c3d3d26f43b6569283f08fec5451a5fc8c98

3. The third TXID output e3710e1da4f947ecfc5162e2e8fa1362c668f16b1c71a20de61b258c939f8a8a contains the original input script that was signed, requires additional online query:

% bx fetch-tx -c ~ / bitcoin-explorer / bx-mainnet-remote.cfg e3710e1da4f947ecfc5162e2e8fa1362c668f16b1c71a20de61b258c939f8a8a

transaction
{
    hash e3710e1da4f947ecfc5162e2e8fa1362c668f16b1c71a20de61b258c939f8a8a
    inputs
    {
        input
        {
            address_hash 3480cd7a92d09974aacc473512ca80a686249498
            previous_output
            {
                hash 4b7b945088ad38de258490d02bdca724548818e1ad184d0e00a2d4d1e82229c8
                index 0
            }
            script "(3046022100da2122351174582ca4f8b9cfc2567bd2c95c3f30be13ce0f20422ba6c2d55806022100af211740671144cc8cbce04e8028e60eb1028af661a8eba77430e4a8615925da01) (02416953ece00bbc3a1ebca108c8961abae0bcc613ecf838bb0e5799202fbe7ae4)"
            sequence 4294967295
        }
    }
    lock_time 0
    outputs
    {
        output
        {
            address_hash ead65b0c5d7abc0af467ae2f34ed1b84a6662fda
            script "dup hash160 (ead65b0c5d7abc0af467ae2f34ed1b84a6662fda) equalverify checksig"
            value 12557630
        }
        output
        {
            address_hash 59cca2f8c91a9784c6c38da5a10f00644238b527
            script "dup hash160 (59cca2f8c91a9784c6c38da5a10f00644238b527) equalverify checksig"
            value 10100000
        }
        output
        {
            address_hash a0d48c129cfde8f124a16f4d69bc47fd7fb5780d
            script "dup hash160 (a0d48c129cfde8f124a16f4d69bc47fd7fb5780d) equalverify checksig"
            value 61334886998
        }
    }
    version 1
}

ASCII encoded script = "dup hash160 (a0d48c129cfde8f124a16f4d69bc47fd7fb5780d) equalverify checksig"

and calculate the corresponding P2PKH address:

% echo a0d48c129cfde8f124a16f4d69bc47fd7fb5780d | bx address-encoding -v 0

1FfPjjFG1uoA62yiTsje8biYYvEhf8puQP

4. For self-awareness, calculate the Hex-encoded script and the associated sha256 value:

% echo "dup hash160 (a0d48c129cfde8f124a16f4d69bc47fd7fb5780d) equalverify checksig" | bx script encoding

76a914a0d48c129cfde8f124a16f4d69bc47fd7fb5780d88ac

% echo 76a914a0d48c129cfde8f124a16f4d69bc47fd7fb5780d88ac | bx sha256
0d9288118ccdc74e6ce85ced746aa48afbd30eb70f58e4ce009a78dd96faf33d

5. Confirm that the signature is valid using an offline command:

Echo 01000000018a8a9f938c251be60da2711c6bf168c66213fae8e26251fcec47f9a41d0e71e3020000006b483045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d012103c0f217eb4428c61d47d8aa084a28c3d3d26f43b6569283f08fec5451a5fc8c98ffffffff0200803801000000001976a914d2c6b9c7f146ea4039e6ae67904eb94d479b7ed688ac06d79e460e0000001976a914b85f8cde95fe9b30872e49d5b961a4af5d07518688ac00000000% | bx input-validate -i 0 03c0f217eb4428c61d47d8aa084a28c3d3d26f43b6569283f08fec5451a5fc8c98 "hash160 dup (a0d48c129cfde8f124a16f4d69bc47fd7fb5780d) equalverify checksig" 3045022100ad775acd2d0b14904771c28754e0e510ecd8af842732c5c15a0899d1e28ed42902204efb34805a958174f6a6273444cde7f97cf38cec0d96d17c7921490f58e6379d01

The endorsement is valid.

segregated token: can I build a raw segwit transaction without segwit entries?

I am trying to build a segwit transaction between a normal p2pkh address and a p2sh 2-of-2 multi-signature address. I've done successful round-trip transactions between these two addresses before (Testnet), but now I want to implement a segwit transaction. However, when I try to transmit the transaction, it says "unexpected token payload for non-witness script …". I see the default witness field as "b & # 39; x00 & # 39;".

Upon further documentation on the subject, I discovered that "If all the txins in a transaction are not associated with any token data, the transaction MUST be serialized in the original transaction format, with no marker, flag, and token."

Does this mean that in order for me to test my segwit code, I will have to wait until I get a segwit entry somehow?

This is my hexadecimal transaction:

01000000000102575307b5cd2a1364c48501434790c0e83c22a16a4b5a902b62e46a34bca06a81000000006b483045022100e07aeaa18e08dedbeebfa7c7299dad2a5dd18df0b31af2f654f2a139d5c6f3900220286b641f4a444d23c952cded85939177abbc7510f909f156fadef5399e20dbe8012103e07f96e5ba598431c0c994493a4ae988c9854c171d5d4bb140db0a27a4c853e4fffffffff53d3533ab79d8425526a7378c91a718e8b526ca32e317b4193333949c261ec9000000006a4730440220780a21e18feeddecb6ca999370fe76a8b612dbaca18ea1249bc312da32f4534c02207342a4d9daea5bbc314e1965f952fbc7fcfcfa5b3b208efc9f2fe0f380afa39b012103e07f96e5ba598431c0c994493a4ae988c9854c171d5d4bb140db0a27a4c853e4ffffffff02102700000000000017a914c104b576f5436309587aefa3ddddd5c295b904808702db1d00000000001976a91452903efc1004de01883ba3687be2a8ea4f6b1b1988ac0100010000000000