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.
901b033b4f8f276420145fe057b776d0d85faa3df95245f764f76704192ce71d
Both payments are on their chains and locked to the same secret hash 14a67841171113571187ef0a9a4fb2202d5fd502, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 901b033b4f8f276420145fe057b776d0d85faa3df95245f764f76704192ce71d
- MakerPaymentSpent: d17df93f62a828c20d1d07ff4a2096ad157c59b1f7d973d73d32981ac8b8ea09
85c94126a2f217e550812356ad0e605ddf02fba39ddf440c110fb689ccd4dad6
Both payments are on their chains and locked to the same secret hash 14a67841171113571187ef0a9a4fb2202d5fd502, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a4aa8c683f09c7d6429638d4911ebcf72e72b0609e3b6e50ff0c36af9e98f6eb
- TakerPaymentSent · TakerPaymentReceived: 85c94126a2f217e550812356ad0e605ddf02fba39ddf440c110fb689ccd4dad6
- TakerPaymentSpent: 1e5716edd0971fe2f9a40bafd105b34fb29148bf83e9a45319fc70905549695a
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.