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.
960854fae8f5eb2e10922f57497ffb8ebb3a08908d9aed78a378fe555b99a175
Both payments are on their chains and locked to the same secret hash c02160ab6177044ab69ef5fc3300ae999e77da58, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 960854fae8f5eb2e10922f57497ffb8ebb3a08908d9aed78a378fe555b99a175
- MakerPaymentSpent: bcfbd6cb0abccb298e05369f325c21cb06d6e29a617df9c894139ba3e0d2787b
132f5b95a1834a047737f5942471a4be0fae7489293b5987e61bb6b8d6ff3398
Both payments are on their chains and locked to the same secret hash c02160ab6177044ab69ef5fc3300ae999e77da58, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b36ac30edb62fc4bff8db9a011ef2578a53973b2582337583cfd881f498cbaf3
- TakerPaymentReceived · TakerPaymentSent: 132f5b95a1834a047737f5942471a4be0fae7489293b5987e61bb6b8d6ff3398
- TakerPaymentSpent: 42c950094069a4c6baacb170ec86e1c233851cc6bb70517ec7d73854eb0bdea8
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.