Transaction

Hash
151e0d0cb7759868a3f89255207725844f3c33257950ee5402d932b5fca25a9d
Block
535422 · 2018-06-19 14:34 · 306,261 confirmations
Data
memo-message
Size
402 bytes
Fee
404 sats (1.00497508 sat/B)

SwingerCat
2136d
I'd like to understand zero-confirmations and why this is safe in BCH? Is this because, no matter what, all broadcasting transactions are included in the following block? Can't this be exploited ?

Inputs (1)

Index
0
Previous Output
SwingerCat
30440220781192de55ebc912fb3f7d6743761bbc2ce350459a4813057e5df6ec328485e3022070efeddd2993b32cad0d20a904cf0288ae0be730a6d60849cfb91ce3dc9659ca41 02104abdeab8d6fcd8ac82e8a23b80991ed53ab685a2cf4164a29e2358b7405aed

Outputs (2)

Index
0
SwingerCat
OP_DUP OP_HASH160 03efcb53218764f40fcf58fb822a48e9cc190ac0 OP_EQUALVERIFY OP_CHECKSIG
Index
1
Type
OP_RETURN
OP_RETURN 6d02 492764206c696b6520746f20756e6465727374616e64207a65726f2d636f6e6669726d6174696f6e7320616e64207768792074686973206973207361666520696e204243483f204973207468697320626563617573652c206e6f206d617474657220776861742c20616c6c2062726f616463617374696e67207472616e73616374696f6e732061726520696e636c7564656420696e2074686520666f6c6c6f77696e6720626c6f636b3f2043616e27742074686973206265206578706c6f69746564203f

Raw

01000000018c072308b5c1d9446cb74c2d63943f3976ee00e0ca5807f69cbdbe32ed31fc6a020000006a4730440220781192de55ebc912fb3f7d6743761bbc2ce350459a4813057e5df6ec328485e3022070efeddd2993b32cad0d20a904cf0288ae0be730a6d60849cfb91ce3dc9659ca412102104abdeab8d6fcd8ac82e8a23b80991ed53ab685a2cf4164a29e2358b7405aedffffffff02de110000000000001976a91403efcb53218764f40fcf58fb822a48e9cc190ac088ac0000000000000000ca6a026d024cc4492764206c696b6520746f20756e6465727374616e64207a65726f2d636f6e6669726d6174696f6e7320616e64207768792074686973206973207361666520696e204243483f204973207468697320626563617573652c206e6f206d617474657220776861742c20616c6c2062726f616463617374696e67207472616e73616374696f6e732061726520696e636c7564656420696e2074686520666f6c6c6f77696e6720626c6f636b3f2043616e27742074686973206265206578706c6f69746564203f00000000