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.
69608f9d425905c7b194548cd52eb659c6a5b276278f8f05ae94d671efdbf7fb
Both payments are on their chains and locked to the same secret hash a14045d82a31db6a1003faf528566dadfafe3a0f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 69608f9d425905c7b194548cd52eb659c6a5b276278f8f05ae94d671efdbf7fb
- MakerPaymentSpent: 27b223218300f61164ee0e755a71a7ebf711a9f69e94853b67ed2920595fa296
aadfdc37eec92624b2b0308eb573553cf0a7032cd930777d34f3e4f1d0d25bba
Both payments are on their chains and locked to the same secret hash a14045d82a31db6a1003faf528566dadfafe3a0f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 381d06206915654bd54fc170be197c95b4fe9e3989b0954ab2305a9165551b37
- TakerPaymentSent · TakerPaymentReceived: aadfdc37eec92624b2b0308eb573553cf0a7032cd930777d34f3e4f1d0d25bba
- TakerPaymentSpent: 59f242fd6c46fdfc2a7a8ce39b43a21d3a2a328d443b9acfd2019f357e85237e
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.