Transaction

Hash
3ae493d59d2c65c5e1857835fface7a32853063aad945256b103a4001df2a634
Block
570564 · 2019-02-19 18:23 · 271,205 confirmations
Data
memo-like
Size
271 bytes
Fee
278 sats (1.02583027 sat/B)

1884d
Any devs here who has time to help Yeeld (POS) implement BCH support? Look here:

https://www.reddit.com/r/Bitcoincash/comments/asce4y/yeeld_needs_help_implementing_bitcoin_cash/

Inputs (1)

Index
0
Previous Output
Fnuller15
304402206e42c8445d4f3dc391a85852c7a0d234f2ad42e0b2049affd04b086bbc7383e0022071b06217974babcf0f474b7b6691f521c9ba61302a4e8a23dc7ca9492001332941 03d195ef370b877d2cd62ce4982fe44c260d2eb3578e09fc480a2c46c9bf92ba71

Outputs (3)

Index
0
Fnuller15
OP_DUP OP_HASH160 2013a9012d85b44c5ff305729c1e6b71fa1e48d6 OP_EQUALVERIFY OP_CHECKSIG
Index
1
Type
OP_RETURN
OP_RETURN 6d04 a6e250428a9c6015f5801d061be2b2cade939e688d389aba9e8c19668cd14c55
Index
2
OP_DUP OP_HASH160 d676f85fae9dfe8e1f5a825bf634f30482993351 OP_EQUALVERIFY OP_CHECKSIG

Raw

01000000016b2484fb9a4e6eb2cde0848a9180ec1af3a9be02d6306eefe7d3a5af3eca7a74000000006a47304402206e42c8445d4f3dc391a85852c7a0d234f2ad42e0b2049affd04b086bbc7383e0022071b06217974babcf0f474b7b6691f521c9ba61302a4e8a23dc7ca94920013329412103d195ef370b877d2cd62ce4982fe44c260d2eb3578e09fc480a2c46c9bf92ba71ffffffff03d2ad0000000000001976a9142013a9012d85b44c5ff305729c1e6b71fa1e48d688ac0000000000000000256a026d0420a6e250428a9c6015f5801d061be2b2cade939e688d389aba9e8c19668cd14c5537020000000000001976a914d676f85fae9dfe8e1f5a825bf634f3048299335188ac00000000