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.
f31a060aca3dc6c230a924a01104cd0afc472519a81dc1a606cc13192f3a8813
Both payments are on their chains and locked to the same secret hash e780c4d7096b0ff4a4e4e246995ec60e4276ea7c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f31a060aca3dc6c230a924a01104cd0afc472519a81dc1a606cc13192f3a8813
- MakerPaymentSpent: b329a98b0015fc7561ed68463e9095c58f8fc88fbd40f661ab13fba2539e2212
6e2b5972c2ce5ff4f87f2e6e17f739f17b2ba4280310225191b2a70c5c9fe05f
Both payments are on their chains and locked to the same secret hash e780c4d7096b0ff4a4e4e246995ec60e4276ea7c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cf928a42be46aeb8076c410dc7305df6e56d209da8e3b34727d449a9f5f59ed0
- TakerPaymentSent · TakerPaymentReceived: 6e2b5972c2ce5ff4f87f2e6e17f739f17b2ba4280310225191b2a70c5c9fe05f
- TakerPaymentSpent: 019e8228363ae462493b02c9499dd63ba50e6dab318f95a269d2df59a09c06df
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.