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.
bfe2d3f6a9ecc493fabbe3b49251a1d086e1ab29ffe59dc35e92cc3a00079352
Both payments are on their chains and locked to the same secret hash 6545f6bd1531203207ef872e8b7d0991108620e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bfe2d3f6a9ecc493fabbe3b49251a1d086e1ab29ffe59dc35e92cc3a00079352
- MakerPaymentSpent: 78696bcc66caad75839c15ea185d96130efab78b6c2b6436d5712137b5f6a849
db950744809d7badb85a4a4b931a65151c1eff8573e595345d0226b6a012c387
Both payments are on their chains and locked to the same secret hash 6545f6bd1531203207ef872e8b7d0991108620e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ef12ff6bd45150d959d23fa0bf78675d5371a8e08ed06e5bcc62e6204abe82a2
- TakerPaymentSent · TakerPaymentReceived: db950744809d7badb85a4a4b931a65151c1eff8573e595345d0226b6a012c387
- TakerPaymentSpent: 7cd89d523b76d660a1710365bc26bdfea8a2de9bc9aa6b568260b0def89b7e1f
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.