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.
19033ca162edc11983e96829ee83e23a6fb03c4f2c214aa45edfb43caaac7471
Both payments are on their chains and locked to the same secret hash 87ccecf0fbaaebe581aea792e0e237c8cbded527, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 19033ca162edc11983e96829ee83e23a6fb03c4f2c214aa45edfb43caaac7471
- MakerPaymentSpent: db72186e1109ac9cb198ae399a5f3a1a4702fbd38eabf8c19714d1eda5ea3322
43d2ec1ececff2350fc59e8da62a4aeb53fe574188f893f717e04327dd8a9d77
Both payments are on their chains and locked to the same secret hash 87ccecf0fbaaebe581aea792e0e237c8cbded527, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b9a62f14f1c722ea66e961f551b1df8d60a58adeec7a7d59f335ef036104c817
- TakerPaymentSent · TakerPaymentReceived: 43d2ec1ececff2350fc59e8da62a4aeb53fe574188f893f717e04327dd8a9d77
- TakerPaymentSpent: 4816dc9f815786f2282cb44ffb5d50f1badad218655d57524a594dbe4ff11940
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.