APIs About Classic View

Transaction

ceba08bfb3310e26b69fdbc4c4a3166e35a3dc1ed0b417ab1e012a08f404a9eb

000000000000000001b5ee6728cfe306d4c34e29440fc5e3b4dbc689f3efd654

Fee Paid

0.00000428 BSV(0.0000178 BSV - 0.00001352 BSV)

Fee Rate

1,019 sat/KB

Confirmations

223,216

Timestamp (utc)

2020-01-29 16:12:59

Version

1

420 B

1 Input

Total Input: 0.0000178 BSV

#0
135izCJEVX1H2719cLYvjcLfGTwmdVULC1
via da9a41c5e2fc861df17c4fdc29ddb55343d93bb4004b16572122f9e9e1ea6fff [0]
0.0000178 BSV

2 Outputs

Total Output: 0.00001352 BSV

#0
135izCJEVX1H2719cLYvjcLfGTwmdVULC1
spent 9e9861981dbb80ad2ea29d5d6a28a843d142bc66eecad4d39b442d9c1683c6ce [0]
0.00001352 BSV
#1
memo.cash - Reply to memo
0 BSV
jm ;WÏ}VX®$Q(9TRD.N37Ñfñ¹´YxLµrelated question (currently working on script decoding) - is the MEMO plan to span beyond the 6dxx space ? The protocol seems to stick to 6d - is there room for "extras"?
https://whatsonchain.com/tx/ceba08bfb3310e26b69fdbc4c4a3166e35a3dc1ed0b417ab1e012a08f404a9eb
jm ;WÏ}VX®$Q(9TRD.N37Ñfñ¹´YxLµrelated question (currently working on script decoding) - is the MEMO plan to span beyond the 6dxx space ? The protocol seems to stick to 6d - is there room for "extras"?