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.
a7ee717640397bdb10de51922e560242677df89ac38ea5f4c61e1022613a0d40
Both payments are on their chains and locked to the same secret hash 5e8814de74a0a59c2fec704ec71e0ddf60284a76, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a7ee717640397bdb10de51922e560242677df89ac38ea5f4c61e1022613a0d40
- MakerPaymentSpent: a61076ac98831de7421ba8ba2d2a3a231fbc6cb04a40328a635e40e977ca11c7
883ad02eb0967c3155a0065e323a42f10f2743650c557c7c27f55d41b688176d
Both payments are on their chains and locked to the same secret hash 5e8814de74a0a59c2fec704ec71e0ddf60284a76, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6a4feceac7ae3652268cf0e1d42fb5dd609f488930085030f84a893752529aa4
- TakerPaymentSent · TakerPaymentReceived: 883ad02eb0967c3155a0065e323a42f10f2743650c557c7c27f55d41b688176d
- TakerPaymentSpent: 76cdd565013700b024f32bf4ff993f08a657a07d5766a0d7ef0f463d44874c3a
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.