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.
d8e6ee908cee980047cfae7c8fcf0e85a8816bec105e415b6cd07d2912ef11a3
Both payments are on their chains and locked to the same secret hash 49ce5e4d18366689581e49c43fd3d19585e95e02, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d8e6ee908cee980047cfae7c8fcf0e85a8816bec105e415b6cd07d2912ef11a3
- MakerPaymentSpent: 21b3eea34a6ec9dba055a291b280d910c1f2dbf19600cc9bf2e393328864cae7
8d92be263f05e2249b454015f2a79424e0e4892e91a3f6b3d07bd4f9ef053e70
Both payments are on their chains and locked to the same secret hash 49ce5e4d18366689581e49c43fd3d19585e95e02, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b2ca120a7e590655816b76d5306a3094dffebb02f39584d19e09f293a75c3d62
- TakerPaymentSent · TakerPaymentReceived: 8d92be263f05e2249b454015f2a79424e0e4892e91a3f6b3d07bd4f9ef053e70
- TakerPaymentSpent: 929efb9324f5203ee38aec8d0087eea41389b2272280d4346bba5e0378267d3d
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.