APIs About Classic View

Transaction

57b32e0c045b27134bd292dde93be60b4f04c3955a26dc2d04a23583b27264ff

000000000000000000a7ac33800a5dfffdcc1859db63cb87ec263c7e86fa2584

Fee Paid

0.00000429 BSV(0.00005232 BSV - 0.00004803 BSV)

Fee Rate

1.019 sat/B

Confirmations

285,430

Timestamp (utc)

2018-11-15 09:18:14

Version

1

421 B

1 Input

Total Input: 0.00005232 BSV

#0
1DmJDXemngwgtPS4kyhsn7EiuADZBxqbZQ
via 95e9147e24c87013cad1ce8738e7580adcc13ac25843a1203bd8d280c47665d2 [0]
0.00005232 BSV

2 Outputs

Total Output: 0.00004803 BSV

#0
1DmJDXemngwgtPS4kyhsn7EiuADZBxqbZQ
spent 1d6d5dfdb3d5fcbe076a4967710af5d0786effc7d347271d32764df3ab5e9537 [0]
0.00004803 BSV
#1
memo.cash - Reply to memo
0 BSV
jm L£õgPûH}ÂkÎ×Y6 R¦Nä^ÍSÒ\L¶I guess that fear of volatility is a driving factor here. As the BCH hashwar escalates BTC might trigger another fee event and bot trading acts on such data without understanding it.
https://whatsonchain.com/tx/57b32e0c045b27134bd292dde93be60b4f04c3955a26dc2d04a23583b27264ff
jm L£õgPûH}ÂkÎ×Y6 R¦Nä^ÍSÒ\L¶I guess that fear of volatility is a driving factor here. As the BCH hashwar escalates BTC might trigger another fee event and bot trading acts on such data without understanding it.