An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
2216030f473089278420afbc2d8393f31612e06e2b8473f866434d0a5c46a939
Both payments are on their chains and locked to the same secret hash a83fa8408fdb5a1e911e1db3187f7736a1cacce9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 2216030f473089278420afbc2d8393f31612e06e2b8473f866434d0a5c46a939
- MakerPaymentReceived · 2216030f473089278420afbc2d8393f31612e06e2b8473f866434d0a5c46a939
- MakerPaymentSpent · 02a78c9cebd79c392ad8cb8a4fc9d2f752946fa54932670ce0060346cd4c829b
13afb9615b1e58eea6ef78975e299524c57088c49b10e486c969dfc7d1b4f7e5
Both payments are on their chains and locked to the same secret hash a83fa8408fdb5a1e911e1db3187f7736a1cacce9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · b6003a082178c921a3057afb93a44120eece8e22d5b16bc9d9b7bc762b763c2a
- TakerPaymentReceived · 13afb9615b1e58eea6ef78975e299524c57088c49b10e486c969dfc7d1b4f7e5
- TakerPaymentSpent · 33845ce9933073e8428a0c9b16ccfbacff1a545d917de5532b680a4f367070a5
- TakerFeeSent · b6003a082178c921a3057afb93a44120eece8e22d5b16bc9d9b7bc762b763c2a
- TakerPaymentSent · 13afb9615b1e58eea6ef78975e299524c57088c49b10e486c969dfc7d1b4f7e5
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.