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.
5eb64079946713d41e82af1ecef41eab19fb50140887cce922cd6ab3a5ce8d88
Both payments are on their chains and locked to the same secret hash 017f62e48a698f02a51b70ec9ce865c7a328f4a0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5eb64079946713d41e82af1ecef41eab19fb50140887cce922cd6ab3a5ce8d88
- MakerPaymentSpent: 3f6b5e13883442f90271b8824601adf15fbc85848a9e577b44f0ee8d35343a78
764038c9cdf0c27e7ba2268aca814f361c528477c9b2074ce1ea49197241263f
Both payments are on their chains and locked to the same secret hash 017f62e48a698f02a51b70ec9ce865c7a328f4a0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1dad5560e6421c66c1c576f3af9aa0bf03ba0bee2f8cc00121cd4883e2514683
- TakerPaymentSent · TakerPaymentReceived: 764038c9cdf0c27e7ba2268aca814f361c528477c9b2074ce1ea49197241263f
- TakerPaymentSpent: ea56b1de625c5f00a7700c12a113288eebfd8a7aa720c267f473e4433bffecd1
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.