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.
fa17113c61efdc25902665d035db0944202414761b7ad1d8ee5da6fea3fca851
Both payments are on their chains and locked to the same secret hash c9eabf9d26a7666e69000ed538466e1dd2257b32, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fa17113c61efdc25902665d035db0944202414761b7ad1d8ee5da6fea3fca851
- MakerPaymentSpent: 52eb748786f2efce23b55641dc1726869a670f8171eb1759f977e0532e2c4207
2a08f02e8930addfb4c975d441321dd39228f041efa5bd5c50958b91c341722c
Both payments are on their chains and locked to the same secret hash c9eabf9d26a7666e69000ed538466e1dd2257b32, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 51e0b50c01389ea704f6a31b62f47c23fe45fa64d9a2892fe59d7ece94a55a97
- TakerPaymentSent · TakerPaymentReceived: 2a08f02e8930addfb4c975d441321dd39228f041efa5bd5c50958b91c341722c
- TakerPaymentSpent: 1762d5b1268a8a1a33281dce4eb8d817cfc7171ecc6a0d3fc355ea6672725922
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.