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.
f9253cba034bdea15aa22db7d9fe05b499018d44e58294b04ce406de1f6e8f40
Both payments are on their chains and locked to the same secret hash 3506e1157722b364813ae50d1f56a208c5b833cf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f9253cba034bdea15aa22db7d9fe05b499018d44e58294b04ce406de1f6e8f40
- MakerPaymentSpent: 708462641c74c583b0819341d21d8cee76a3af96a15995095e75caa663ea55fb
731330d3685950368ce8f2666f0b21797b6b49c0ae0f2cf7928f3fb542068217
Both payments are on their chains and locked to the same secret hash 3506e1157722b364813ae50d1f56a208c5b833cf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7761256ed6ea1e0aa564712cde44e0743f9a905abc94cceea37e9b651f0b5f89
- TakerPaymentSent · TakerPaymentReceived: 731330d3685950368ce8f2666f0b21797b6b49c0ae0f2cf7928f3fb542068217
- TakerPaymentSpent: 90bec01d227750612a8cf45d6e3a5e1f5f0f95a12f4c9a03d193a4795203d4ac
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.