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.
28c0193d2bd12c6276b8a655f031e341579201cb590704f472bdde00713b87c6
Both payments are on their chains and locked to the same secret hash fa97d4ef45270254b586ba91ec4ea12d1316974d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 28c0193d2bd12c6276b8a655f031e341579201cb590704f472bdde00713b87c6
- MakerPaymentSpent: 843a1c376863d7f178fce64d3ff713ad60ad5ec9ce52972bebfc7a0e919f4d64
ed37066a31a42a5707c5161e73adb4257410777045b9c832158d364df4b8810c
Both payments are on their chains and locked to the same secret hash fa97d4ef45270254b586ba91ec4ea12d1316974d, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentSent · TakerPaymentReceived: ed37066a31a42a5707c5161e73adb4257410777045b9c832158d364df4b8810c
- TakerPaymentSpent: d94096069ff83c8c81b13f93b9ed29869cdef73617652487cae21f07941c67d5
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.