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.
bff23e2c246cbc30640a6bfe50c2838ed9a1362605b3837fc642b4b9ecb878f1
Both payments are on their chains and locked to the same secret hash c90d8e11de8c27f841778d36bbcb1bfafe69b684, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bff23e2c246cbc30640a6bfe50c2838ed9a1362605b3837fc642b4b9ecb878f1
- MakerPaymentSpent: 2153330116ee44d4894fff38f0ac8f005729a5039180267fdb46ab37986df400
3f96c50815b0a392813381e62f001a0c6afd73225178e39ccb4aa986b2363101
Both payments are on their chains and locked to the same secret hash c90d8e11de8c27f841778d36bbcb1bfafe69b684, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0b35532ec1c4fe85cfde65ba0c16ef01902fe196e95130446a99b2ad0aa23494
- TakerPaymentSent · TakerPaymentReceived: 3f96c50815b0a392813381e62f001a0c6afd73225178e39ccb4aa986b2363101
- TakerPaymentSpent: 72d239ea2352eb492a16240ea36b66bff25291f4cc44e73d5133cf06507c33bf
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.