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.
5e5ac4d91edbc4c79cab0003aa660b304d6a1a30f361fb68816e4daca631fd2d
Both payments are on their chains and locked to the same secret hash 480091f148a25736d18ce2e198ec68c20272ce20, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5e5ac4d91edbc4c79cab0003aa660b304d6a1a30f361fb68816e4daca631fd2d
61647e803f229a4a1d7c471763e4ac94e92d0b4a60cc34595b1a2ad0fcd37b3c
Both payments are on their chains and locked to the same secret hash 480091f148a25736d18ce2e198ec68c20272ce20, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: f75f47be98e15fb099a460f988f9e442d40fa154af02d08b22d13031bbd3213e
- TakerPaymentReceived: 61647e803f229a4a1d7c471763e4ac94e92d0b4a60cc34595b1a2ad0fcd37b3c
- TakerPaymentSpent: 9d696e0933dffd8e30f0ad83fd6eb5bd745aab4d9cd58561277361749c850d18
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.