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.
4c35106bd96b62b93e56ccb777c25bc1a767f6601a596b9192097d11018eebfc
Both payments are on their chains and locked to the same secret hash c3634cdc91218f0d5546d047650d44a8a4f03c04, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4c35106bd96b62b93e56ccb777c25bc1a767f6601a596b9192097d11018eebfc
- MakerPaymentSpent: 2337bb60c5051a33cb23da7a01f73f61271ddab6545dbe520a03a7170b851401
350abde2103b42f62623195c1ba574336dbe54adfafa68556b74f75c54c92238
Both payments are on their chains and locked to the same secret hash c3634cdc91218f0d5546d047650d44a8a4f03c04, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 494fad69b585b9eeef437d41cbb3324eba132b42981e7d64e95b5be6b6407041
- TakerPaymentSent · TakerPaymentReceived: 350abde2103b42f62623195c1ba574336dbe54adfafa68556b74f75c54c92238
- TakerPaymentSpent: 596ddd3c658baee82854f929655be5732807e6d06b11d90229245122fbd3e891
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.