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.
e22b4ace38c07323d051efd8905440968a65b8050816e026af9eadaf3af36f3c
Both payments are on their chains and locked to the same secret hash 70e485c30a222a1e499888357e25f523948f974d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e22b4ace38c07323d051efd8905440968a65b8050816e026af9eadaf3af36f3c
- MakerPaymentSpent: 5217506e6a58d152b8599d71b1a3666cca1fcf80b58e12ee221f8baecd42b0c7
cc9b5bdc42b4d4c5e273c794694db29082847b87caaf3101902d0323bdf6c93e
Both payments are on their chains and locked to the same secret hash 70e485c30a222a1e499888357e25f523948f974d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: d30da4ee307735cc5f2cf29643f950a8b010636525469b8db58fcd9130262371
- TakerPaymentReceived · TakerPaymentSent: cc9b5bdc42b4d4c5e273c794694db29082847b87caaf3101902d0323bdf6c93e
- TakerPaymentSpent: ad33b2df974668b05912b8792add97d464dce3e7f91448e5ae7bf8785f0432ea
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.