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.
6fdb80ba32cc78b7e9a016d839366db77f6159ffd7a6b79bad8f45f346cb85f1
Both payments are on their chains and locked to the same secret hash fc556641b4e03fa82ce1ec5bdf19493f57d1ab28, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6fdb80ba32cc78b7e9a016d839366db77f6159ffd7a6b79bad8f45f346cb85f1
- MakerPaymentSpent: bebec8334c34f21c11aa3cd21b4d835c62769570128c88d8a708fcb3c6f1e63c
e20a79b2b7d00490c556039ca4c21d5911cc2ee1ce5cfd5b24a5f055d9d6c1e1
Both payments are on their chains and locked to the same secret hash fc556641b4e03fa82ce1ec5bdf19493f57d1ab28, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 601ac0b8f10c538f609d816833b2dc5cbae9ff0920b93613adb33dc9a52723fa
- TakerPaymentSent · TakerPaymentReceived: e20a79b2b7d00490c556039ca4c21d5911cc2ee1ce5cfd5b24a5f055d9d6c1e1
- TakerPaymentSpent: b4d08a110dfdbbc432edd46481e0be7dfb33ed9e78092e124af34ec1cd524983
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.