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.
e18c9dc528bd60e550755ecd6ff0406350e3417345d12d7a9cb577a1c5b520c6
Both payments are on their chains and locked to the same secret hash b90197bae2dd4327f0ee796ca01063e492b25eb0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e18c9dc528bd60e550755ecd6ff0406350e3417345d12d7a9cb577a1c5b520c6
- MakerPaymentSpent: 73c86ed44d0960ce53a2d0c473a0d236f88254c8e612e6f46ea0c0a34b49d8c1
255d99e068e2dd93843ef13177bc000e687b6009e80d2e78b7a873cc906eb17f
Both payments are on their chains and locked to the same secret hash b90197bae2dd4327f0ee796ca01063e492b25eb0, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentSent · TakerPaymentReceived: 255d99e068e2dd93843ef13177bc000e687b6009e80d2e78b7a873cc906eb17f
- TakerPaymentSpent: e48bd66676c3ae1995c90cc58edb6b6c943038f0282f256a97a82921b1f34e5e
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.