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.
33f695a4c4bead3798218f2f309ffe46f85526cb7c044f3af9267568ebf43ce0
Both payments are on their chains and locked to the same secret hash b17fd8bfdf72eecd55d479a83a4ba800c8421c0d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 33f695a4c4bead3798218f2f309ffe46f85526cb7c044f3af9267568ebf43ce0
- MakerPaymentSpent: 50eb8c70679e9bcbfa38c0e0983dd0ac9df52ab46b59411cc97b39731196ded8
2aab7c3d1e92905eff627bd980468d98d169408a3b6d8b9095ed04b62701091e
Both payments are on their chains and locked to the same secret hash b17fd8bfdf72eecd55d479a83a4ba800c8421c0d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 28e7476ceacf847a47cdffc1c6e79562166152019c2c357f1c5e5b69661eab2f
- TakerPaymentSent · TakerPaymentReceived: 2aab7c3d1e92905eff627bd980468d98d169408a3b6d8b9095ed04b62701091e
- TakerPaymentSpent: fb7512c016c07e76e230d9045b1beb9e66a54b6de756c0abb9d3b7a89dd708b5
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.