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.
f7cace82187389bea9a79b66132df85c77c17bf639287c7abc506314bc7107f8
Both payments are on their chains and locked to the same secret hash 5893684ae8503344d7dfe363c54c98dac093bd4a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f7cace82187389bea9a79b66132df85c77c17bf639287c7abc506314bc7107f8
- MakerPaymentSpent: 29b1d2dcaae348c23b58be942d019b6115da957cf8c0fb65fc80e1e05c24ca79
d39bae271ccb80471f08b67d89895049524446178391e0b654486a19e39de111
Both payments are on their chains and locked to the same secret hash 5893684ae8503344d7dfe363c54c98dac093bd4a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: aff64be81d7fbf37668d47c7928e27fe0ac45580ff0218f7e6d154ebb97d3676
- TakerPaymentSent · TakerPaymentReceived: d39bae271ccb80471f08b67d89895049524446178391e0b654486a19e39de111
- TakerPaymentSpent: 4ddeaa55e4cfa4e26c3f7923e00f05792fa78c6f7d17e2ad56dc4c86f3f65efd
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.