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.
80b20b7ed8ca555aae53297ac80333d638be747791c4171f042f25422867aa25
Both payments are on their chains and locked to the same secret hash 2731b3e9ebb48b10031edc2c7b6bc0ec37a9acb6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 80b20b7ed8ca555aae53297ac80333d638be747791c4171f042f25422867aa25
- MakerPaymentSpent: 69cd84a59f53b68b00ecb14179e50701d62e7a8dacf616a534ee18ef0d978be4
4f7fd2afda06096a23b8fa846de16a01124f301ce5b0120039176aa6a6997327
Both payments are on their chains and locked to the same secret hash 2731b3e9ebb48b10031edc2c7b6bc0ec37a9acb6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 59a2d78cc41b72dfd61b48a39b15448131a721437f92733bd05b21c83983dc86
- TakerPaymentSent · TakerPaymentReceived: 4f7fd2afda06096a23b8fa846de16a01124f301ce5b0120039176aa6a6997327
- TakerPaymentSpent: 93deae7ead7fd9a4243292d8e7f749172a74d05e218f79251eca7d8a6c937992
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.