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.
8ee0c8767f930d2fe0df72abccf7969aa386f9f305fda0c51ca54a539a4930af
Both payments are on their chains and locked to the same secret hash 142aca967b8c1913602ae731fbb27057943c1489, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8ee0c8767f930d2fe0df72abccf7969aa386f9f305fda0c51ca54a539a4930af
- MakerPaymentSpent: 56b015a9226e3db0ad064242c2728c9a3894df0015c0062001fd147e1d7e89b5
4ceaaccb5ab67d5854cddbb5206abe7767ef391a45be73ba2838675f10ae93fc
Both payments are on their chains and locked to the same secret hash 142aca967b8c1913602ae731fbb27057943c1489, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4c9eb98a79df8b955721a41a03fb6706c49e346289d43c59674152a150d622be
- TakerPaymentSent · TakerPaymentReceived: 4ceaaccb5ab67d5854cddbb5206abe7767ef391a45be73ba2838675f10ae93fc
- TakerPaymentSpent: feeffd6fab1e602af38531dd8a0f4bdebacf03f1932754e17341dcfcbbfd84ed
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.