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.
b5194eee89252f350d77449b1b1a62c1a8b6a80c63a8cd28e2e69441cb0efb9c
Both payments are on their chains and locked to the same secret hash bd1cad8d7293972d25237726c6193e080a25ebae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b5194eee89252f350d77449b1b1a62c1a8b6a80c63a8cd28e2e69441cb0efb9c
- MakerPaymentSpent: f98120972933fbeecb859630f610f2a56cfde21c4210d7be9b3d5da8bf9b65bd
1c795ba5c32e72ba1e5b333b145dc03f5b8af624423961f0606974a03e4a1c2a
Both payments are on their chains and locked to the same secret hash bd1cad8d7293972d25237726c6193e080a25ebae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23e8e32776012111c0e8d889aec7e5ae684cfe16d800b43f8a33c914b3ac5cd8
- TakerPaymentSent · TakerPaymentReceived: 1c795ba5c32e72ba1e5b333b145dc03f5b8af624423961f0606974a03e4a1c2a
- TakerPaymentSpent: 3cca2869d85365adda67a880a0f6805f275c7539348e97655c9c2019b80c105a
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.