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.
94e184f0ffabcdcca9cd9f4a02e4236963e31bb299b8d1a697fb50448a8d522a
Both payments are on their chains and locked to the same secret hash e86cec8f2a82f62ea73e2ad0052b90f09c5fb30e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 94e184f0ffabcdcca9cd9f4a02e4236963e31bb299b8d1a697fb50448a8d522a
- MakerPaymentSpent: a3a8fb921ee3420227702668845de8cccb5f7571f4ef48fb09d9d360b5b96401
3cfebe5eeb17b067789b8fc62e999d92e2571fe8a73c9e7559ff1d3acde3d199
Both payments are on their chains and locked to the same secret hash e86cec8f2a82f62ea73e2ad0052b90f09c5fb30e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 811d63c12134691ebf8fb017971584ce44b88fc7c5033487c2f5a2eb1ca33d3b
- TakerPaymentSent · TakerPaymentReceived: 3cfebe5eeb17b067789b8fc62e999d92e2571fe8a73c9e7559ff1d3acde3d199
- TakerPaymentSpent: 5f6254c7e64916ecdb7da31dddc36cb883285c73aff76f384827468a10f56f9f
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.