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.
9d2db47af59f2a9cc7b9ab1ff2e47abe141a690de993ad2d476623afb69a2d08
Both payments are on their chains and locked to the same secret hash 799382e7e3369e949e132e9a73837d32747bcb07, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9d2db47af59f2a9cc7b9ab1ff2e47abe141a690de993ad2d476623afb69a2d08
- MakerPaymentSpent: 3eeb52ac3a4fa92daddedd9e61c732b9187412f05e4379ebf7c815c556c56eba
7cb68201595c688ea969e874a37332ffa46df86d696fb13782abeb0caa754d1c
Both payments are on their chains and locked to the same secret hash 799382e7e3369e949e132e9a73837d32747bcb07, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f3cc37eba96330344227d1f37103a496684e4a7bf89665271ca3c9b6a659232e
- TakerPaymentSent · TakerPaymentReceived: 7cb68201595c688ea969e874a37332ffa46df86d696fb13782abeb0caa754d1c
- TakerPaymentSpent: 20978df321d6125eb7cb4020139a1683abace5ae563e0070f3dd111866986d6c
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.