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.
631d15c8bc9f98bb83a0add982112b89467734c7f75a88b623bee7ef2cd01a0f
Both payments are on their chains and locked to the same secret hash e26fd72cbe837f78b3cd79e3df4314a40eb04116, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 631d15c8bc9f98bb83a0add982112b89467734c7f75a88b623bee7ef2cd01a0f
- MakerPaymentSpent: 0e2800bb47d047c02e6c22e8bae249819ecaacf9ab13d4a7ac65e71473875f94
00ffaed044242f6d778542e656aca189e628172d338b2635626ec6ada5765ca9
Both payments are on their chains and locked to the same secret hash e26fd72cbe837f78b3cd79e3df4314a40eb04116, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fe539d7d0e03aae651d7434bd05efa1daf6fec24cdb77d974329d3e88ff929b7
- TakerPaymentSent · TakerPaymentReceived: 00ffaed044242f6d778542e656aca189e628172d338b2635626ec6ada5765ca9
- TakerPaymentSpent: b5048a080d15b7fa6a428269e46b2bc406293321fd40cec58d03681f8b2e2530
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.