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.
94437af424f600559e56a25fabab1b9375694eb1a45b8e7b3316986a4ca1a43e
Both payments are on their chains and locked to the same secret hash ec2f0f2b0c812ecce17cba7d2b8f108ed3e5fe1e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 94437af424f600559e56a25fabab1b9375694eb1a45b8e7b3316986a4ca1a43e
- MakerPaymentSpent: bc4c419d6bb37139fdb61d0960af9a5233e5c933175d869b7c3ed15d0bdb16b9
79e309389bdaceba6da36d2811d2aedb06415115ae4a1b5bb687f50c9584df33
Both payments are on their chains and locked to the same secret hash ec2f0f2b0c812ecce17cba7d2b8f108ed3e5fe1e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3d7d6ad0af56f17ef24fa4eea176bef62a2e3ee4048ff3e11c0a856ee173183e
- TakerPaymentSent · TakerPaymentReceived: 79e309389bdaceba6da36d2811d2aedb06415115ae4a1b5bb687f50c9584df33
- TakerPaymentSpent: 0182167f4964f7d7147935bf065690d8a9a8d9b5e5e96ed29462cc7f0a1dc589
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.