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.
f34a1482b28d8d84a511729b73352902d8c805c01e74ef1f73d0d5960c61bba5
Both payments are on their chains and locked to the same secret hash 039728d76cd0e32ba99f2eb8ef6341aec92ec62b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f34a1482b28d8d84a511729b73352902d8c805c01e74ef1f73d0d5960c61bba5
- MakerPaymentSpent: 8ab5a0b481cdad6aa67e105227bea639eb0ece449c463e4948a6143dd3dba419
5583c2eced6bd3a217eafee7b95c684af8cfcdac5defe778475921c005f5774a
Both payments are on their chains and locked to the same secret hash 039728d76cd0e32ba99f2eb8ef6341aec92ec62b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 13756dddfbe15c1e665798c1b26920fbd7b2f02c2eb72ebb3139ed13e4e45f04
- TakerPaymentSent · TakerPaymentReceived: 5583c2eced6bd3a217eafee7b95c684af8cfcdac5defe778475921c005f5774a
- TakerPaymentSpent: 317119f35cd40977be09d345ab2a61c12d6202f14eb579184da6024ebefda2a1
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.