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.
e7e636c04cf8dd43cce0e65377df799f6616fc5646faba0404608a6069187a5c
Both payments are on their chains and locked to the same secret hash e88891ffaa5fbd80f66e918095acb9cd86a91413, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e7e636c04cf8dd43cce0e65377df799f6616fc5646faba0404608a6069187a5c
- MakerPaymentSpent: 093e482f1763264e1e3604dbfa52aadad0603037f486dcdcb4f7c2a6aa6151bd
808ed5468163adf3d2905ec00fd740d08869a2de11b17400a68397a6b3c59cd7
Both payments are on their chains and locked to the same secret hash e88891ffaa5fbd80f66e918095acb9cd86a91413, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f75aaecd81bf67323f5aa6f9a51be1bb06462653a5ba9bcc1aa3232e07515a8a
- TakerPaymentReceived · TakerPaymentSent: 808ed5468163adf3d2905ec00fd740d08869a2de11b17400a68397a6b3c59cd7
- TakerPaymentSpent: e3a49a77c3523f98944585fedb8593e67b66950c374b0bb7b72a3bbc657578be
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.