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.
e07552a11030fc3bcd053a16c2e1592e41fd27b044fe560ceee6ac6054a76d8d
Both payments are on their chains and locked to the same secret hash 7327406b1d02b1811cbc72326a3ebd1c3064790d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e07552a11030fc3bcd053a16c2e1592e41fd27b044fe560ceee6ac6054a76d8d
- MakerPaymentSpent: bfac5167eb9b6607d4436d7cae3e34ce54a28020d8fe7aa1c5c1252d2343bb32
984068400b7c9ada72f833af83e7090bc2706bd1aee4c754bf2b92a725db293f
Both payments are on their chains and locked to the same secret hash 7327406b1d02b1811cbc72326a3ebd1c3064790d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 86f3bb78dda1da632478334173981c4075f89a59bf66bf1de0a8aca0ade34918
- TakerPaymentSent · TakerPaymentReceived: 984068400b7c9ada72f833af83e7090bc2706bd1aee4c754bf2b92a725db293f
- TakerPaymentSpent: 696374bbd77859259c6f9fa7d29815e9431b91455a1d2b513c6bc6e9e0861ca9
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.