APIs About Classic View

Transaction

f13f068afcbbb411e6b9dbed8582fc1351e36f5d1712f2a698f5e0449c26dd36

000000000000000000981e2d1091fda25514807a0868d7a676fa267d368dc8c0

Fee Paid

0.00000422 BSV(0.00837938 BSV - 0.00837516 BSV)

Fee Rate

1.016 sat/B

Confirmations

303,391

Timestamp (utc)

2018-07-12 17:36:54

Version

1

415 B

1 Input

Total Input: 0.00837938 BSV

#0
1CVgnAKwpEmL9TJHJJ8bWYtcLSaoYaC7VC
via 1fcbb01f54a204c1c497305a6ecf0c69d8441481bd4da147bf58be89265b5ec6 [0]
0.00837938 BSV

2 Outputs

Total Output: 0.00837516 BSV

#0
1CVgnAKwpEmL9TJHJJ8bWYtcLSaoYaC7VC
spent dcbbbb32b2d2f591d4d7a418258fdb9badc4064b1398ccf812050b9144e22af6 [0]
0.00837516 BSV
#1
memo.cash - Reply to memo
0 BSV
jm 4LªC¯èÀUFøp]\¬÷Æ¤©z£]¸ß¬L¯402 is then obviously obsolete, since it has gained no traction, and crypto has. I don't really understand where HTTP 402 comes into play when regarding crypto micropayments.
https://whatsonchain.com/tx/f13f068afcbbb411e6b9dbed8582fc1351e36f5d1712f2a698f5e0449c26dd36
jm 4LªC¯èÀUFøp]\¬÷Æ¤©z£]¸ß¬L¯402 is then obviously obsolete, since it has gained no traction, and crypto has. I don't really understand where HTTP 402 comes into play when regarding crypto micropayments.