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.
684de0b79dbe99491170d920e02a8d5bf5dc9c4c833fac5d546e2eb4ac1227e1
Both payments are on their chains and locked to the same secret hash e05cadbd1d1dabc7ef7f791955dcaade87cfa42f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 684de0b79dbe99491170d920e02a8d5bf5dc9c4c833fac5d546e2eb4ac1227e1
a80c2a80ce4cf54d19e1f17d94ec1e756c2f5290f56937b8178f6e4f87bbec63
Both payments are on their chains and locked to the same secret hash e05cadbd1d1dabc7ef7f791955dcaade87cfa42f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · f5c42394265338c6d0f16c446b90fad8ee68b5c0c61dca292c74e121248b6b9a
- TakerPaymentReceived · a80c2a80ce4cf54d19e1f17d94ec1e756c2f5290f56937b8178f6e4f87bbec63
- TakerPaymentSpent · 6a4c557aa11c5e29891f216c2dfbf34413ad6bb4d086552de17b76d91add301d
No anomalies were recorded against this swap.
Reported by kdf-statsdb.