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.
57178f6c468e2c823b62f3f312b1904b83db2f14cd2a91d8bafa8d2c9f30f324
Both payments are on their chains and locked to the same secret hash 085e52ba49f8eafb50009dee4ad31b31522ec1c4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 57178f6c468e2c823b62f3f312b1904b83db2f14cd2a91d8bafa8d2c9f30f324
- MakerPaymentSpent: 7ec4407ff457ef9719eb915215e6ce98de773116bf1125b59006ba8f25863ab6
ccc7eb1cd9f9c1f48a79ae1e51e19e2da8e9efacf33be8783b0bbd433cd1ab93
Both payments are on their chains and locked to the same secret hash 085e52ba49f8eafb50009dee4ad31b31522ec1c4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9b2449f6c772ac91fa361c42ce35233f34971ac56a16ad78cb4ed68a3fe6e451
- TakerPaymentSent · TakerPaymentReceived: ccc7eb1cd9f9c1f48a79ae1e51e19e2da8e9efacf33be8783b0bbd433cd1ab93
- TakerPaymentSpent: aa978d6b45eb296b1fa47e3ad34ecf6a942ad988aeee47f8f763e783e33c0cd3
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.