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.
8c71bfa256cf6991499bdd065cdaa38c15c2a9f7c57f7345c65ad29e73c96717
Both payments are on their chains and locked to the same secret hash 4786da9ca7b2122c8619e4c07a94ddf71fa5a490, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8c71bfa256cf6991499bdd065cdaa38c15c2a9f7c57f7345c65ad29e73c96717
- MakerPaymentSpent: 83cddd5bedbd34d4d6050fce1377152d0354925341fb27ac4eb1cf77fa1aec5e
c89e9c0296c43b6bef4dbe1470626290f30644bdf0cfd2554150155c5f9f4abc
Both payments are on their chains and locked to the same secret hash 4786da9ca7b2122c8619e4c07a94ddf71fa5a490, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7b2728f590279fe3fb486247755c1fd41ffeac457374c7c528498cc6b916470c
- TakerPaymentSent · TakerPaymentReceived: c89e9c0296c43b6bef4dbe1470626290f30644bdf0cfd2554150155c5f9f4abc
- TakerPaymentSpent: 6aab193cf0f0a5ba55ef191684c254969f6b1283197d973a570f20d89fe3940b
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.