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.
6b758c17f80bfdad0e3eea9b306330ff27ce5211438bcfd7b577c9c32c40e5d2
Both payments are on their chains and locked to the same secret hash 300a456046865843e614a39e601ad5f71e444c01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6b758c17f80bfdad0e3eea9b306330ff27ce5211438bcfd7b577c9c32c40e5d2
- MakerPaymentSpent: a3616e5d481706525795e07b82f25d960d754ca869ba4987344510f14ccbfa0f
84f234b9ce99a4a9142870c1f2a4b78b44dd21066fcd6507912493c3033616d4
Both payments are on their chains and locked to the same secret hash 300a456046865843e614a39e601ad5f71e444c01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: df7d7544ceadcab5851192d458aed68cd2db949a827e2d53821c6368fc83407a
- TakerPaymentSent · TakerPaymentReceived: 84f234b9ce99a4a9142870c1f2a4b78b44dd21066fcd6507912493c3033616d4
- TakerPaymentSpent: fd4856934ecc85982efdfa060f2df5a49f63a35c31453cf835d0e99410fffeba
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.