Transaction

376d059c81b0ca1f93e36c275bc4dbdb02b4bfccdfe516b3ed858d811ccec847
2024-09-07 07:16:27
0.00000004 BSV
(
0.00300995 BSV
-
0.00300991 BSV
)
3.093 sat/KB
1
53,153
1,293 B

3 Outputs

Total Output:
0.00300991 BSV
  • jmetaB03bcd76c7340b907c0cc396ff1efaf38cc6e1fe339232fc35038c812a06a1992e6@6e310a0579acad2cd4035426f1abe6c508d443dd4241600efb7c245ddb21c7da atom.entry metarss.netM{<entry> <title type="text">Asynchronous IO: the next billion-dollar mistake?</title> <id>https://yorickpeterse.com/articles/asynchronous-io-the-next-billion-dollar-mistake/</id> <updated>2024-09-07T05:53:10.146675Z</updated> <link href="https://yorickpeterse.com/articles/asynchronous-io-the-next-billion-dollar-mistake/"/> <author> <name>signa11</name> <uri>https://news.ycombinator.com/user?id=signa11</uri> </author> <content type="html">Asynchronous IO allows handling many IO operations without blocking threads, but it&#39;s a complex solution that may not be necessary if OS threads were more efficient. &lt;a href=&#34;https://hackernews.betacat.io/#asynchronous-io-the-next-billion-dollar-mistake&#34; target=&#34;_blank&#34;&gt;[summary]&lt;/a&gt; &lt;a href=&#34;https://news.ycombinator.com/item?id=41471707&#34; target=&#34;_blank&#34;&gt;[comments]&lt;/a&gt;</content> </entry>
    https://whatsonchain.com/tx/376d059c81b0ca1f93e36c275bc4dbdb02b4bfccdfe516b3ed858d811ccec847