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.
9a8c57ef0173f20e77b1e1242490bfb003c67b43d4ee1942f67545c154948e2c
Both payments are on their chains and locked to the same secret hash 11f3f493ca3612765532f586d2959cb75aa3660f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a8c57ef0173f20e77b1e1242490bfb003c67b43d4ee1942f67545c154948e2c
- MakerPaymentSpent: c65dad2d9918c7dcc8c1659822d152a693215c998fad502e69704dc99d0fb7cd
092344403d313a9f109dfc3e3f62d695223e5648797391baeb4d259b3679ffed
Both payments are on their chains and locked to the same secret hash 11f3f493ca3612765532f586d2959cb75aa3660f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 076e8cf3c6bae6a8418850b95aeb04aa77fdd72ac230cc9e43c0210cd15fc5de
- TakerPaymentSent · TakerPaymentReceived: 092344403d313a9f109dfc3e3f62d695223e5648797391baeb4d259b3679ffed
- TakerPaymentSpent: 9f248fe244db80820c6a012536609cdba547bcadb3bd2224587dd5aa6aa38e07
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.