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.
fc1c3366087b1346dd92a282c14e2edbf658b5165fa4e75cd663af93a1d497ca
Both payments are on their chains and locked to the same secret hash 22f99bd848bb60ca06053cbbe192e7e5e6dbd807, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fc1c3366087b1346dd92a282c14e2edbf658b5165fa4e75cd663af93a1d497ca
- MakerPaymentSpent: a07d945c1027b920516a96c184e09598ce0c7d3dcd946c8123e3b88f084764bf
c66cdacb9b53c5607a14be17d07c2559f73cce41dd0e8fc0acfe049724884781
Both payments are on their chains and locked to the same secret hash 22f99bd848bb60ca06053cbbe192e7e5e6dbd807, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bad3a12da98906a435182c2253a19ea48c89a90ebf3670cb682bc827d6bb05b5
- TakerPaymentSent · TakerPaymentReceived: c66cdacb9b53c5607a14be17d07c2559f73cce41dd0e8fc0acfe049724884781
- TakerPaymentSpent: 8a1c201957c57317ceac442af59352682c4dee37f87a7f264b8de4f77632c6b1
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.