Transaction 5d0d4e3b…4498e2ea 5d0d4e3b752da537d94e47f55bfe09210503f3b584cf8d184224da 2f4498e2ea Status
Confirmed441,458 confirmations Value flow Ribbon height is proportional to value. 0.00415076 BCH in from 1 input, 0.00414704 BCH out to 2 outputs, 372 sat to the miner.
Settlement check Input total
0.00415076
BCH, 1 input
Output total
0.00414704
BCH, 2 outputs
Miner fee
372 sat
0.00000372 BCH, inputs minus outputs
Fee rate
1.09 sat/B
fee ÷ size
Size
340 B
version 2, locktime 0
CashTokens
None
no token prefix on any output
Balances: 0.00415076 BCH in = 0.00414704 BCH out + 372 sat fee.
Inputs1 · 0.00415076 BCH Prevout lookups resolved: 1 / 1 # Address and previous output Type Amount Scripts 0 qzntnhvk…ctemjut5 Spends 4ff452bf42…760a163392:1 P2PKH 0.00415076 BCH ‹/› Scripts Previous output 4ff452bf42713140f2f2dec68139c980fb2a6e2866e31d22f92911760a163392:1
Unlock type Unlocking script · 107-byte input script
Previous output script 25-byte pay-to-public-key-hash output
Unlocking script · 107 bytes
<0x3045022100ae15e5491fe4cd44332721c5da1bd74781d7dcc502bbafd66b11fa0f9eb5e30b022058a684b455be7e9177fca0fe50f70122fb379532fb9708372599d0e163edc32b41>
<0x0207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250c> 483045022100ae15e5491fe4cd44332721c5da1bd74781d7dcc502bbafd66b11fa0f9eb5e30b022058a684b455be7e9177fca0fe50f70122fb379532fb9708372599d0e163edc32b41210207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250c Prevout locking script · 25 bytes
OP_DUP
OP_HASH160
<0xa6b9dd96fb60e0dbbcba88a43976573c0c3c3a43>
OP_EQUALVERIFY
OP_CHECKSIG 76a914a6b9dd96fb60e0dbbcba88a43976573c0c3c3a4388ac
Outputs2 · 0.00414704 BCH Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent. # Address Type Spent Amount Scripts 0 script dcee291707…6f763143 Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “BETLGY7y_oe' ."M@e"z"NxfXc2V<ORBq1@9*n(f…”
Locking script bytes · 139 bytes
OP_RETURN
<0x00424554>
<0x010382e0475905370592bc795f6f6527cf84a988d38c81f00af3a6cb2e224dfa9d40e26522aad2817af1229b8a4e78d7ab66f6e81958a363f832563cf0bf08c804144ff452bf42713140f2f2dec68139c980fb2a6e2866e31d22f92911760a1633920207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250c> 6a04004245544c83010382e0475905370592bc795f6f6527cf84a988d38c81f00af3a6cb2e224dfa9d40e26522aad2817af1229b8a4e78d7ab66f6e81958a363f832563cf0bf08c804144ff452bf42713140f2f2dec68139c980fb2a6e2866e31d22f92911760a1633920207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250c 1 qzntnhvk…ctemjut5 spent in 6689b…2c54:00.00414704 BCH ‹/› Scripts
Position in block 536,363 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 61,285 Merkle proof The proof lists the sibling hashes that lift this transaction to the Merkle root in block 536,363's header. Check it offline against that header.
This page does not load the path itself; the proof download holds it.
Raw transaction340 bytes Copy hex02000000 019233160a761129f9221de366286e2afb80c93981c6def2f240317142bf52f44f010000006b483045022100ae15e5491fe4cd44332721c5da1bd74781d7dcc502bbafd66b11fa0f9eb5e30b022058a684b455be7e9177fca0fe50f70122fb379532fb9708372599d0e163edc32b41210207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250cffffffff02…a914a6b9dd96fb60e0dbbcba88a43976573c0c3c3a4388ac00000000 Show full hex 02000000019233160a761129f9221de366286e2afb80c93981c6def2f240317142bf52f44f010000006b483045022100ae15e5491fe4cd44332721c5da1bd74781d7dcc502bbafd66b11fa0f9eb5e30b022058a684b455be7e9177fca0fe50f70122fb379532fb9708372599d0e163edc32b41210207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250cffffffff0200000000000000008b6a04004245544c83010382e0475905370592bc795f6f6527cf84a988d38c81f00af3a6cb2e224dfa9d40e26522aad2817af1229b8a4e78d7ab66f6e81958a363f832563cf0bf08c804144ff452bf42713140f2f2dec68139c980fb2a6e2866e31d22f92911760a1633920207ee3c3969ba4cce824b611a45c5958158044ccc720599ab64eee7a319d6250cf0530600000000001976a914a6b9dd96fb60e0dbbcba88a43976573c0c3c3a4388ac00000000 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.00415076 BCH Show scenario JSON Loading payload...