Confirmed transaction d041cef54028219c4cb4e055a42f65bccd7474abddee00539f85db 3d4967bbbb Status
Confirmed444,659 confirmations Value flow Ribbon height is proportional to value. 0.00041097 BCH in from 1 input, 0.00040760 BCH out to 2 outputs, 337 sat to the miner.
Settlement check Input total
0.00041097
BCH, 1 input
Output total
0.00040760
BCH, 2 outputs
Miner fee
337 sat
0.00000337 BCH, inputs minus outputs
Fee rate
1.00 sat/B
fee ÷ size
Size
337 B
version 1, locktime 0
CashTokens
None
no token prefix on any output
Balances: 0.00041097 BCH in = 0.00040760 BCH out + 337 sat fee.
Inputs1 · 0.00041097 BCH Prevout lookups resolved: 1 / 1 # Address and previous output Type Amount Scripts 0 qr3rngd3…s092qznj Spends c79c802eb5…344061f3f8:0 P2PKH 0.00041097 BCH ‹/› Scripts Previous output c79c802eb52dc26d56b62955feffa5817dcd018608dc17060938e2344061f3f8:0
Unlock type Unlocking script · 107-byte input script
Previous output script 25-byte pay-to-public-key-hash output
Unlocking script · 107 bytes
<0x3045022100e0ae4edeeefdb3827f369dd8e3f88bec3d8994469305a343b110f5fdd7d3b46e02203849b79ce76c50ee1983f4e1bc473ca0f967a0b4f4a402629fccdc620c70fe1d41>
<0x0255ee1308b007eb7196f63f863ed2934290485f2dc4d25104118a9d1709e0dab9> 483045022100e0ae4edeeefdb3827f369dd8e3f88bec3d8994469305a343b110f5fdd7d3b46e02203849b79ce76c50ee1983f4e1bc473ca0f967a0b4f4a402629fccdc620c70fe1d41210255ee1308b007eb7196f63f863ed2934290485f2dc4d25104118a9d1709e0dab9 Prevout locking script · 25 bytes
OP_DUP
OP_HASH160
<0xe239a1b17fa065b6dc64d2e7bec1216567838761>
OP_EQUALVERIFY
OP_CHECKSIG 76a914e239a1b17fa065b6dc64d2e7bec121656783876188ac
Outputs2 · 0.00040760 BCH Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent. # Address Type Spent Amount Scripts 0 qr3rngd3…s092qznj spent in f9453a3670…f0417b9a0a:00.00040760 BCH ‹/› Scripts 1 script 2ff9614dba…d7f62e49 Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “mmoneyL|Have you read all this: https://…”
Locking script bytes · 136 bytes
OP_RETURN
<0x6d0c>
<0x6d6f6e6579>
<0x4861766520796f75207265616420616c6c20746869733a2068747470733a2f2f646f63732e676f6f676c652e636f6d2f70726573656e746174696f6e2f642f31656a77464469776b566231794f2d3050694b75797853697169716f434169576b2d58724b626e31325861552f656469743f7573703d73686172696e67> 6a026d0c056d6f6e65794c7c4861766520796f75207265616420616c6c20746869733a2068747470733a2f2f646f63732e676f6f676c652e636f6d2f70726573656e746174696f6e2f642f31656a77464469776b566231794f2d3050694b75797853697169716f434169576b2d58724b626e31325861552f656469743f7573703d73686172696e67
Position in block 531,992 Open the block The tile strip needs the block's transaction list, which this page does not load. Open the block for its tile grid.
Byte offset in block 88,373 Merkle proof The proof lists the sibling hashes that lift this transaction to the Merkle root in block 531,992's header. Check it offline against that header.
This page does not load the path itself; the proof download holds it.
Raw transaction337 bytes Copy hex01000000 01f8f3614034e238090617dc088601cd7d81a5fffe5529b6566dc22db52e809cc7000000006b483045022100e0ae4edeeefdb3827f369dd8e3f88bec3d8994469305a343b110f5fdd7d3b46e02203849b79ce76c50ee1983f4e1bc473ca0f967a0b4f4a402629fccdc620c70fe1d41210255ee1308b007eb7196f63f863ed2934290485f2dc4d25104118a9d1709e0dab9ffffffff02…626e31325861552f656469743f7573703d73686172696e6700000000 Show full hex 0100000001f8f3614034e238090617dc088601cd7d81a5fffe5529b6566dc22db52e809cc7000000006b483045022100e0ae4edeeefdb3827f369dd8e3f88bec3d8994469305a343b110f5fdd7d3b46e02203849b79ce76c50ee1983f4e1bc473ca0f967a0b4f4a402629fccdc620c70fe1d41210255ee1308b007eb7196f63f863ed2934290485f2dc4d25104118a9d1709e0dab9ffffffff02389f0000000000001976a914e239a1b17fa065b6dc64d2e7bec121656783876188ac0000000000000000886a026d0c056d6f6e65794c7c4861766520796f75207265616420616c6c20746869733a2068747470733a2f2f646f63732e676f6f676c652e636f6d2f70726573656e746174696f6e2f642f31656a77464469776b566231794f2d3050694b75797853697169716f434169576b2d58724b626e31325861552f656469743f7573703d73686172696e6700000000 Bitauth scenario libauth wallet template JSON A scenario bundles this transaction with the outputs it spends, so each unlocking script can be stepped through op by op in Bitauth IDE and its signature check re-run against the exact source outputs.
Source outputs 1 · 0.00041097 BCH Show scenario JSON Loading payload...