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.
3b74035e8a1c13399d2b4145ff162610963d0646cfd5eab9b3e27f679805c426
Both payments are on their chains and locked to the same secret hash 88d8a09355aec3d377431c5747b8bff75a08bb05, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 3b74035e8a1c13399d2b4145ff162610963d0646cfd5eab9b3e27f679805c426
95555bb58e931a8bb32c1acee7f0f92009cc064345c93cbb50a0dd29f53efef4
Both payments are on their chains and locked to the same secret hash 88d8a09355aec3d377431c5747b8bff75a08bb05, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 10fcc7f87d402d0364c04f193c2fea4b231eb6a9c952ae0fa2af6c8d3e731c9f
- TakerPaymentReceived: 95555bb58e931a8bb32c1acee7f0f92009cc064345c93cbb50a0dd29f53efef4
- TakerPaymentSpent: a46d4f264c9252890fadb6f9943aa6bd98c3e2b4aa4ee7a99bcfaff52709543f
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.