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.
4c1fcf6e7c8eeca755634a57442415436f8962f613af0e07afe2d9ef62dcda61
Both payments are on their chains and locked to the same secret hash 30c7cb85da0e616541c7cac0db661f3d1f0e2897, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: 4c1fcf6e7c8eeca755634a57442415436f8962f613af0e07afe2d9ef62dcda61
- MakerPaymentSpent: ddb44d97b5035062d145efbc8707f1e82224212222a07d4c6af762a5f81b02d9
cfcdb171f440299a7062538cb3cd783838d94ef7a88e5cf5a3a2e80e13e12342
Both payments are on their chains and locked to the same secret hash 30c7cb85da0e616541c7cac0db661f3d1f0e2897, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: ed260ecc615db7ecbbc420f9da64cf7205ee6e5e5968b6d85ec59898dc226cbd
- TakerPaymentSent: cfcdb171f440299a7062538cb3cd783838d94ef7a88e5cf5a3a2e80e13e12342
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.