APIs About Classic View

Transaction

3e9de62951be4693f8037133cd192dca4ed774a4c9af70ccf7c6a1ff76afa1db

00000000000000000652284aa6d05113d79d8383c94b1541dad91cae9aab79e2

Fee Paid

0.00000391 BSV(0.00002509 BSV - 0.00002118 BSV)

Fee Rate

1.02 sat/B

Confirmations

267,181

Timestamp (utc)

2019-03-20 12:09:20

Version

1

383 B

1 Input

Total Input: 0.00002509 BSV

#0
1LYz8FKHp5QHfeowBJsZPuGXzzbNwez4ao
via f8a5c3574ba01ddca4a99212d1455ed568efa6f057cb24b8cb87ee26c9525510 [0]
0.00002509 BSV

2 Outputs

Total Output: 0.00002118 BSV

#0
1LYz8FKHp5QHfeowBJsZPuGXzzbNwez4ao
spent 91b19500010167c9d83dde725007e7d44de680b419b7af3cf22a074049ed17af [0]
0.00002118 BSV
#1
memo.cash - Reply to memo
0 BSV
jm M=¶óûb(¦5¦þiæ§,Ø+-è£Ê;LWhy not make the blocking more like a "sort away" feature. On an open ledger doing a "hard block" in the UI is somewhat weird anyway, isn't it?
https://whatsonchain.com/tx/3e9de62951be4693f8037133cd192dca4ed774a4c9af70ccf7c6a1ff76afa1db
jm M=¶óûb(¦5¦þiæ§,Ø+-è£Ê;LWhy not make the blocking more like a "sort away" feature. On an open ledger doing a "hard block" in the UI is somewhat weird anyway, isn't it?