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.
05d075fc914049cad65f46037a7169761b40704777be7783b28f599ac8cde925
Both payments are on their chains and locked to the same secret hash 976d77ca1e686b60baa491e17ce74d8fe65b98d9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 05d075fc914049cad65f46037a7169761b40704777be7783b28f599ac8cde925
- MakerPaymentSpent: 7dd07cd987461f766256c33b6e6595dce6d50380ff7dc7e0b4b33acbe2772cee
f9c33cfdb37b9c603eb5f729dcb973eb1ad6ba4969325f00ffc5bc6062d65d57
Both payments are on their chains and locked to the same secret hash 976d77ca1e686b60baa491e17ce74d8fe65b98d9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea0e88057a042c8005687ee53fe20642417751d19b0e7c71bd262743d05f0780
- TakerPaymentSent · TakerPaymentReceived: f9c33cfdb37b9c603eb5f729dcb973eb1ad6ba4969325f00ffc5bc6062d65d57
- TakerPaymentSpent: fe0f56eeb29763035b26d127b33d8029912f917b68569c525846f19fd15e51f6
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.