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.
331ab6d6f94796bb1f8feb7b6701a6d1b113ef9961d7fb753bda2023e4d83198
Both payments are on their chains and locked to the same secret hash 469bbe0d52248ab963ae752d9cfd672712859c25, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 331ab6d6f94796bb1f8feb7b6701a6d1b113ef9961d7fb753bda2023e4d83198
- MakerPaymentSpent: 2be1e9d29848bd97f5a9d21856dca9b5f6b3e2d45262a5f96e4b5d6fa309f64c
bdce866359ca656e557187a8d0e3b001160e09055dc18920314b99a66f8c5894
Both payments are on their chains and locked to the same secret hash 469bbe0d52248ab963ae752d9cfd672712859c25, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ca29a6e9af1d061f89815a13055b299469c27bc0fa78ccc2f760b3cb255dfab9
- TakerPaymentSent · TakerPaymentReceived: bdce866359ca656e557187a8d0e3b001160e09055dc18920314b99a66f8c5894
- TakerPaymentSpent: 416d56d4cbe6a167dec793f28681fbca9f05cbef6576788a1b69fda62164d039
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.