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.
097a9a7199e0438718408f333d2447a1b666a327657dcbd84e97141c27f5f4ba
Both payments are on their chains and locked to the same secret hash 424263416c48e7a8dfa321b80132ef948f272149, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 097a9a7199e0438718408f333d2447a1b666a327657dcbd84e97141c27f5f4ba
- MakerPaymentSpent: a4f78c82acdc4229fead1af11de79d9c568842ddf911c8d9f2d6eca8a417ccbe
c75d0436af1ec583b89972a5ddf9eb50f34f53ec78960809f583a1dcca479279
Both payments are on their chains and locked to the same secret hash 424263416c48e7a8dfa321b80132ef948f272149, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cee195b03ec6df89a9fc69b790692cf1d3409c8fdbb7f6d30ab5a8864c84b5b3
- TakerPaymentSent · TakerPaymentReceived: c75d0436af1ec583b89972a5ddf9eb50f34f53ec78960809f583a1dcca479279
- TakerPaymentSpent: d704d9d06c8f5735955da30a7c93b93e1a025d1e9386fa53ff698f66413b8465
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.