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.
551e3d6fb68c749c6ac9c4e0da8c1e18007b93bb7a726cf260940d35853b5759
Both payments are on their chains and locked to the same secret hash 39c414ef7ad6cd279f10502a28b9d082e07d2504, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 551e3d6fb68c749c6ac9c4e0da8c1e18007b93bb7a726cf260940d35853b5759
- MakerPaymentSpent: 66b5773a679d4e0e6bdaca68a5a90251dcce457a3f17bf811b4a8780b8863730
e2a4df8382da7b8062fd6e89530b98af57ede102d7a4c4dd689cd8bbc5b3cc79
Both payments are on their chains and locked to the same secret hash 39c414ef7ad6cd279f10502a28b9d082e07d2504, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 55fa5bc5688d9e7c92158e6d9ea27ae3c1183c2e6ad3bfa25751bf8c34a58ff7
- TakerPaymentSent · TakerPaymentReceived: e2a4df8382da7b8062fd6e89530b98af57ede102d7a4c4dd689cd8bbc5b3cc79
- TakerPaymentSpent: a327e392bc1462ccd68cdba5bf7a5e8e4ef0da4f579ffc6db5e6462929563513
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.