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.
2471db798f377311769b7b2edd12607c375e8cad9905d3c58d525159f4e07858
Both payments are on their chains and locked to the same secret hash ea1f49948f2f807c9deb18ba8de1f52a10d7c1fd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2471db798f377311769b7b2edd12607c375e8cad9905d3c58d525159f4e07858
- MakerPaymentSpent: e0fd4e5097504936c5a88236c738e204b71c0307fdc93c67850ac536eb2a049e
10925e15458df317ece623011de779f963c7511ef7bc64ad3ffe4893384ed799
Both payments are on their chains and locked to the same secret hash ea1f49948f2f807c9deb18ba8de1f52a10d7c1fd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a56aff80f8011c92886098da3ab7e18a3b1d9d8d67e6d32ea5d789b7f4fe3ac3
- TakerPaymentSent · TakerPaymentReceived: 10925e15458df317ece623011de779f963c7511ef7bc64ad3ffe4893384ed799
- TakerPaymentSpent: b06ff32e014714638c2421c4bbb069ae28e4bfcd21d754b3a62cba3ac80eddd2
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.