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.
20e6fbdab9a4c4f4aec5fd6a2778a2b1f555d4586756f755da99b7e49eaaefeb
Both payments are on their chains and locked to the same secret hash c13e9d2e422bf44fd1a0da5f99b287e2de2076e8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 20e6fbdab9a4c4f4aec5fd6a2778a2b1f555d4586756f755da99b7e49eaaefeb
- MakerPaymentSpent: 05bd23c430540cc4ff11f0bed5a358db7df64bd71ced6723e2821ac33f31ceb9
d5f174085514cfb462db4172dbea0ecb77c1ba11aa70fa2e9f8144110fe4e2a9
Both payments are on their chains and locked to the same secret hash c13e9d2e422bf44fd1a0da5f99b287e2de2076e8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: ba9d37986ddc8d13aff909226eb12864dac9ed41c3e3cf978b29220b90c056ab
- TakerPaymentSent · TakerPaymentReceived: d5f174085514cfb462db4172dbea0ecb77c1ba11aa70fa2e9f8144110fe4e2a9
- TakerPaymentSpent: 3ce61d7db37252fa038996295fefad6f26a259857d24e22016882deaec728043
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.