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.
85b9137bac1ba0229164e2da58a9e33fa35a834a1630aa848ef81da463742e1d
Both payments are on their chains and locked to the same secret hash a9ae77555995e4bcf82a8ea92a456ebdb2a793b9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 85b9137bac1ba0229164e2da58a9e33fa35a834a1630aa848ef81da463742e1d
- MakerPaymentSpent: 578b3a59f64dab773244e751966b13ba8a7ea0b3021de201b9cb9e3e8ec11efd
bf865e7ae1df3ad3b3bd68ad3955ac0979260ac80ee5491c48ccb85decbdab75
Both payments are on their chains and locked to the same secret hash a9ae77555995e4bcf82a8ea92a456ebdb2a793b9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 948123651f063e2b6a8dd93482b88479b04736999d59474caa783068e8bd5cc0
- TakerPaymentSent · TakerPaymentReceived: bf865e7ae1df3ad3b3bd68ad3955ac0979260ac80ee5491c48ccb85decbdab75
- TakerPaymentSpent: 533878f6acee852a5f132c26b1d625a333120069fb314974ba4659e024401890
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.