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.
783a2442146338a31ee8c4d2e3d71a144481c7e4c4fbad84ad0bed580db6dd62
Both payments are on their chains and locked to the same secret hash 36342a5e2af4a6a420520ce3010da9e3c66c6fa8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 783a2442146338a31ee8c4d2e3d71a144481c7e4c4fbad84ad0bed580db6dd62
- MakerPaymentSpent: 5b94111a4d20c199dace66914d9fa75eb5b08c70bff3a22b8746a61c73d923ba
c69047b64c618bfc5b998723d0054ddc5c26a521cb0254ff65f2164fcdde4ce1
Both payments are on their chains and locked to the same secret hash 36342a5e2af4a6a420520ce3010da9e3c66c6fa8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 531f2060dd29ca0841b0aa1207f98e6cdb2374ac4303fd4e8a093752c4fd61dd
- TakerPaymentSent · TakerPaymentReceived: c69047b64c618bfc5b998723d0054ddc5c26a521cb0254ff65f2164fcdde4ce1
- TakerPaymentSpent: 6e70c42f2cb2ab9e3e7300442fc5ff0a2b3e55b2fba9a3ac5f62962820246f8a
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.