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.
28941901a2b1956b51728c6b09dc6ca09138aa08d3576acbe420d18d8ca710d4
Both payments are on their chains and locked to the same secret hash 198531edb738502cdf1548d83a783732656ab6a8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 28941901a2b1956b51728c6b09dc6ca09138aa08d3576acbe420d18d8ca710d4
- MakerPaymentSpent: 16e054d9ffa9b09701bc6230affe0f5bd287a62f52a3e52c8ec40e63cdab07d6
82dc9c09e2f86be1f767274f3bc12458d47bae6119d87491b39fc947c5ee220f
Both payments are on their chains and locked to the same secret hash 198531edb738502cdf1548d83a783732656ab6a8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 339bba2b2358847fea84971a853ce64c47c6afae8159b81d5a78ad936c865adc
- TakerPaymentSent · TakerPaymentReceived: 82dc9c09e2f86be1f767274f3bc12458d47bae6119d87491b39fc947c5ee220f
- TakerPaymentSpent: 978cd84d7d2d1a3e01ca553e5ddccd41483ac04012e779f78fd8dd5ecf532e49
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.