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.
06990abc68fa3bfd54eb37ebd2138bdd5fcec66c14e0afff651c83971c9f9ade
Both payments are on their chains and locked to the same secret hash db815ba9c694e2e58a554ffbfbbbdafb44b0f577, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 06990abc68fa3bfd54eb37ebd2138bdd5fcec66c14e0afff651c83971c9f9ade
- MakerPaymentSpent: 727099aceb5678b7b4a811450d886e71b9506cc5150db5696a238d89f8defca8
5ab6398a2aa63655d186f96bad63fa7550ca9351b6a38302491c3a5b094e2ce4
Both payments are on their chains and locked to the same secret hash db815ba9c694e2e58a554ffbfbbbdafb44b0f577, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c895fb9a8cf01e6e844e99d9a4b380aaafad47063fd4d974bfc0f41106ba7496
- TakerPaymentReceived · TakerPaymentSent: 5ab6398a2aa63655d186f96bad63fa7550ca9351b6a38302491c3a5b094e2ce4
- TakerPaymentSpent: 2a583e8c5ed0aba04b561ec4d4c11b1c67b2289d005692ee991de73613d44062
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.