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.
4ed7bb8d8b3f16a5bd5e20f13ab99026166c42577a91185d0a625d3cc93426f8
Both payments are on their chains and locked to the same secret hash a38ec4e395ada81346cb55ccbeab7c28e281df5c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4ed7bb8d8b3f16a5bd5e20f13ab99026166c42577a91185d0a625d3cc93426f8
- MakerPaymentSpent: 503a36044589a46123fc45feb72c0dab89b48577fbdf6b563eeb2698a8a47493
01c9f48ef17d7531055bbaf4953019ca5b6e8705758de51d0640405781dda0e3
Both payments are on their chains and locked to the same secret hash a38ec4e395ada81346cb55ccbeab7c28e281df5c, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentSent · TakerPaymentReceived: 01c9f48ef17d7531055bbaf4953019ca5b6e8705758de51d0640405781dda0e3
- TakerPaymentSpent: 5f45e54b1954b9c13062940cc98910d9c52928bb1089ec9ef8cc3cb548fd3c4e
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.