English
  • 简体中文
Mainnet
BSV
  • BSV
  • mBSV
  • Bits
  • Sat

Transaction

491f7fa42827b5fbcd023dcc5be419de2ec33e66e62d7f49bb86b509fea48d1d
( - )
228,769
2019-11-16 01:00:10
1
1,713 B

4 Outputs

Total Output:
  • j"19HxigV4QyBv3tHpQVcUEQyq1pzZVdoAutMÉ# No. tl;dr - It seems like Twetch uses their own proprietary database to index and store transactions as opposed to scraping directly from the chain. Twetch uses the B:// protocol spec to organize their OP_RETURN data. Here is an example: https://api.whatsonchain.com/v1/bsv/main/tx/hash/550bbd3e980e831703ea963c842efc4ddb0e6d3974c025be414e9789686c2357 However, even if you were to format a custom script with valid parameters and post it on-chain, Twetch wouldn't pick it up since the data is not picked up by their servers directly through the web app, thus, the TXID is not indexed. From Klimenos' blog: "For instance, using those applications, it is possible to post a message on the blockchain using the protocol requirements imposed by Twetch and Weiblock. However, if those platforms are not aware of the transaction, they will not pull them because they are currently not designed with a mechanism that automatically fetch third-party published content from the blockchain. The opposite is also true: it is possible to post content on Twetch and Weiblock without requiring you to broadcast content to the blockchain in the first place." https://blog.bsv.sh/the-weitch-protocol-reversing-the-front-end-part-2/ text/markdownUTF-8 answer.md
    https://whatsonchain.com/tx/491f7fa42827b5fbcd023dcc5be419de2ec33e66e62d7f49bb86b509fea48d1d