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.
ef80eafabaae6af0ed196e6dca2650d907c231de5f7fe0cd6531c76f174f68a6
Both payments are on their chains and locked to the same secret hash fff5bfc96bb10cefde7a966ca93ff8efff9b352a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ef80eafabaae6af0ed196e6dca2650d907c231de5f7fe0cd6531c76f174f68a6
- MakerPaymentSpent: 3d494b66a69fd25964cdf504772e37829c6ae242765e0a1daf1db8f711968a10
201077044d88550d81adedb8375dbfddd66ff1254c51cd6386aaa86ad2e35b99
Both payments are on their chains and locked to the same secret hash fff5bfc96bb10cefde7a966ca93ff8efff9b352a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8f77a3d45fed65b8cbe1150d1800e46ee213247bfbe057c7d8a96227623caee9
- TakerPaymentSent · TakerPaymentReceived: 201077044d88550d81adedb8375dbfddd66ff1254c51cd6386aaa86ad2e35b99
- TakerPaymentSpent: bd982e8013281eaeb20f76009c18b8e4dc6cc7d0783d7e0d062f5e82d43f8996
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.