Confirmed transaction 555bcd85645879bfa8d4b44d7de12ce8b73390b40465d256af6cd2 5dbe0ef9ef Status
Confirmed411,539 confirmations Value flow Ribbon height is proportional to value. 0.00072962 BCH in from 1 input, 0.00072618 BCH out to 2 outputs, 344 sat to the miner.
Settlement check Input total
0.00072962
BCH, 1 input
Output total
0.00072618
BCH, 2 outputs
Miner fee
344 sat
0.00000344 BCH, inputs minus outputs
Fee rate
1.02 sat/B
fee ÷ size
Size
337 B
version 1, locktime 0
CashTokens
None
no token prefix on any output
Balances: 0.00072962 BCH in = 0.00072618 BCH out + 344 sat fee.
Inputs1 · 0.00072962 BCH Prevout lookups resolved: 1 / 1 # Address and previous output Type Amount Scripts 0 qqp6fylj…x2y6aply Spends e24fa43ca1…3dd05789ea:0 P2PKH 0.00072962 BCH ‹/› Scripts Previous output e24fa43ca18d3ab0d225b0722e859f09fa1a3e7d146ae86acb4e9a3dd05789ea:0
Unlock type Unlocking script · 107-byte input script
Previous output script 25-byte pay-to-public-key-hash output
Unlocking script · 107 bytes
<0x3045022100c146812600ec8545e3a141852b19451973375909e4818e38c216697e7f51b5a902206cc7d094b721f29469615dff8f286f2a37da823a84960d702c5c2d5587291f3b41>
<0x03d9c1d0d053637834c8cc5d26391b2e6736b8266a903fbbd05074c99a92ead404> 483045022100c146812600ec8545e3a141852b19451973375909e4818e38c216697e7f51b5a902206cc7d094b721f29469615dff8f286f2a37da823a84960d702c5c2d5587291f3b412103d9c1d0d053637834c8cc5d26391b2e6736b8266a903fbbd05074c99a92ead404 Prevout locking script · 25 bytes
OP_DUP
OP_HASH160
<0x03a493f2a02248c55d889d91379bbb407c2eddc5>
OP_EQUALVERIFY
OP_CHECKSIG 76a91403a493f2a02248c55d889d91379bbb407c2eddc588ac
Outputs2 · 0.00072618 BCH Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent. # Address Type Spent Amount Scripts 0 qqp6fylj…x2y6aply spent in 2c008e88ca…0ff44676b7:00.00072618 BCH ‹/› Scripts 1 script b263ff13d8…010562ce Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “m CapitalismLwIt's funny how often those…”
Locking script bytes · 136 bytes
OP_RETURN
<0x6d0c>
<0x4361706974616c69736d>
<0x497427732066756e6e7920686f77206f6674656e2074686f73652077686f2074616c6b2061626f7574206265696e6720776f726b656420746f2064656174682061726520746865206f6e65732077686f20617265206c617a7920616e6420686172646c792067657420616e7920776f726b20646f6e652e> 6a026d0c0a4361706974616c69736d4c77497427732066756e6e7920686f77206f6674656e2074686f73652077686f2074616c6b2061626f7574206265696e6720776f726b656420746f2064656174682061726520746865206f6e65732077686f20617265206c617a7920616e6420686172646c792067657420616e7920776f726b20646f6e652e
Position in block 564,428 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 6,579 Merkle proof The proof lists the sibling hashes that lift this transaction to the Merkle root in block 564,428'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 01ea8957d03d9a4ecb6ae86a147d3e1afa099f852e72b025d2b03a8da13ca44fe2000000006b483045022100c146812600ec8545e3a141852b19451973375909e4818e38c216697e7f51b5a902206cc7d094b721f29469615dff8f286f2a37da823a84960d702c5c2d5587291f3b412103d9c1d0d053637834c8cc5d26391b2e6736b8266a903fbbd05074c99a92ead404ffffffff02…6172646c792067657420616e7920776f726b20646f6e652e00000000 Show full hex 0100000001ea8957d03d9a4ecb6ae86a147d3e1afa099f852e72b025d2b03a8da13ca44fe2000000006b483045022100c146812600ec8545e3a141852b19451973375909e4818e38c216697e7f51b5a902206cc7d094b721f29469615dff8f286f2a37da823a84960d702c5c2d5587291f3b412103d9c1d0d053637834c8cc5d26391b2e6736b8266a903fbbd05074c99a92ead404ffffffff02aa1b0100000000001976a91403a493f2a02248c55d889d91379bbb407c2eddc588ac0000000000000000886a026d0c0a4361706974616c69736d4c77497427732066756e6e7920686f77206f6674656e2074686f73652077686f2074616c6b2061626f7574206265696e6720776f726b656420746f2064656174682061726520746865206f6e65732077686f20617265206c617a7920616e6420686172646c792067657420616e7920776f726b20646f6e652e00000000 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.00072962 BCH Show scenario JSON Loading payload...