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.
728c8ccb6f1a9f5202c67a718f7d6c5d25f294e805ff14a231bf424ad6616ef9
Both payments are on their chains and locked to the same secret hash 8d22b81ffcc60f97de2d691a1f9f0e60b10be043, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 728c8ccb6f1a9f5202c67a718f7d6c5d25f294e805ff14a231bf424ad6616ef9
- MakerPaymentSpent: 92d055be4f0a789c278d3c95bccc9dc9db716faae532f6b2476a80ae3eeb8a16
f8da0b8d6524892951da67b6051a4bf09c392f058be8b793dd9be21985c9f368
Both payments are on their chains and locked to the same secret hash 8d22b81ffcc60f97de2d691a1f9f0e60b10be043, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 871a8507bc0ef1acd38e15bb78df3c5dc7b7186d0b4a4217fce9b86ba41f3e38
- TakerPaymentSent · TakerPaymentReceived: f8da0b8d6524892951da67b6051a4bf09c392f058be8b793dd9be21985c9f368
- TakerPaymentSpent: 9336f0d6555e8ec6427847b72e3318d70dd05bc3fad159a47a9a3f6e79535981
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.