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.
c3b5159ebafd579e38b59952803745bfb914ca65dbb42313f33feb8b491848f1
Both payments are on their chains and locked to the same secret hash 6c1648b1191c57a40ba52b0525fc0388c7cc60d9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c3b5159ebafd579e38b59952803745bfb914ca65dbb42313f33feb8b491848f1
- MakerPaymentSpent: 182948c35a2d029de5550e858a798c6cb9c4141abb3664a60924132281c12108
026f565a088d8172aef3423a238cdfa779b95fd86cd626b3d1d15c376de8312c
Both payments are on their chains and locked to the same secret hash 6c1648b1191c57a40ba52b0525fc0388c7cc60d9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: af8418e0e5e63e65bc68bdf94d9bfd47205c233540b14a431a9422d8b4c09576
- TakerPaymentSent · TakerPaymentReceived: 026f565a088d8172aef3423a238cdfa779b95fd86cd626b3d1d15c376de8312c
- TakerPaymentSpent: 6d0daed33febc1a420e63ae12145204c037266cbdb8b5be302d8b7ad698a633e
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.