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.
c4d4ca883297e89b7f0c1320527fd15780d2a64b53e24bfacc3a4d06bd94a88e
Both payments are on their chains and locked to the same secret hash 0c792b8bc34b54cc1a962f50ccd2dc2e504e33b3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c4d4ca883297e89b7f0c1320527fd15780d2a64b53e24bfacc3a4d06bd94a88e
- MakerPaymentSpent: 951fc373f63d922967961e28e8048220ddf8a9aa0191357a5f6442846dd0e413
a21dda92bf9c1b0127291835796ffcf194be526dceff35c9a16b479537eb3fd9
Both payments are on their chains and locked to the same secret hash 0c792b8bc34b54cc1a962f50ccd2dc2e504e33b3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e447a8ea516a9937a6a510eab7466c22ff2d4ac970d9a37a114f99839c3334ae
- TakerPaymentSent · TakerPaymentReceived: a21dda92bf9c1b0127291835796ffcf194be526dceff35c9a16b479537eb3fd9
- TakerPaymentSpent: ef315a43ab56739f8d3cff9e0dde5b0d2bc97267a27e5faa8f44ad157002ef14
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.