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.
ae472d7620833ceac1a2e4c41017af3113a52df4c930aad3905e116078cc6e47
Both payments are on their chains and locked to the same secret hash 215ec962b6e4f60ae65fc0a55718dd02f8e4ddf0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ae472d7620833ceac1a2e4c41017af3113a52df4c930aad3905e116078cc6e47
- MakerPaymentSpent: 08f6fe4f0041ae9744e3f57cd8d16f38566bc92f5ff8accd9f363e20ced3738f
dadc751cbfd0498c90ecfa8563b9c6e08604da5ad9aa8cc830292ccc2e44ba3a
Both payments are on their chains and locked to the same secret hash 215ec962b6e4f60ae65fc0a55718dd02f8e4ddf0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ff1d4926f6f8892793baa0797ef28b26502801b73618a2e633797083e42a2852
- TakerPaymentSent · TakerPaymentReceived: dadc751cbfd0498c90ecfa8563b9c6e08604da5ad9aa8cc830292ccc2e44ba3a
- TakerPaymentSpent: fcc381bc65258c34234ed60388d01df60c38747e43e51895280b82407af418aa
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.