Transaction
Copy HashCopy LinkBookmark762338bcb660ff55521d79715dba3ea517b8373bde36d9cc5f48da2d4570a13f
( - )
108,695< 6 confirmations is generally considered too few for high-value transactions. This convention's applicability may vary.
2020-07-13 15:25:10
1
1,199 B
1 Input
Total Input:
- #0via b60dedfc7f277855e864d8d8fa2b0c4259c6caf9339483729a492b5e0382b9e3 [2]b60dedfc7f277855e864d8d8fa2b0c4259c6caf9339483729a492b5e0382b9e3
4 Outputs
Total Output:
- #0bitcom
Print ASCII j"1NF7i6ZoMDXaJ2Q5M9QFriH74ya6r6vP8uB, MAP and AIPMiTwetch transactions use 3 protocols piped together using the [Bitcom pipe convention](https://github.com/unwriter/Bitcom/issues/2). The 3 protocols are: * [B - Bitcoin Simple Storage Protocol](https://b.bitdb.network/) - Stores the twetch file data * [MAP - Magic Attribute Protocol](https://map.sv/) - Contains other twetch-specific attributes and metadata * [AIP - Author Identity Protocol](https://github.com/BitcoinFiles/AUTHOR_IDENTITY_PROTOCOL) - Contains author signature and pubkey If you want a really easy way of decoding the transactions, you could use [Operate](https://www.operatebsv.org) which uses functions on the blockchain to decode all these protocols. I [wrote this article](https://www.operatebsv.org/blog/operate-meets-javascript/) which has an embedded console on the page and instructions for loading and parsing twetch transactions using Operate.