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.
2c155b6360576310a7fc759f8b39781dfd929ec3cf974f3e28458403625144aa
Both payments are on their chains and locked to the same secret hash 114f17870cc2681338b475bd8e2a89acbe668acc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2c155b6360576310a7fc759f8b39781dfd929ec3cf974f3e28458403625144aa
- MakerPaymentSpent: de5e0e738d83b2209f7c163921bdbdde1120657efbff01b0306d5361f70bcee9
3f93cb33356a2c94d33319babca11f4e4b2c08e848c399a0d14a917272967cd2
Both payments are on their chains and locked to the same secret hash 114f17870cc2681338b475bd8e2a89acbe668acc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5a785d762a1f3f91e6d53429d7d510532cb96a78947fc673a034c061f94bd90b
- TakerPaymentSent · TakerPaymentReceived: 3f93cb33356a2c94d33319babca11f4e4b2c08e848c399a0d14a917272967cd2
- TakerPaymentSpent: 8db5591709e0bd67712e4bfc46849b7c5833e343fe2b2c30ae2a5619da18369a
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.