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.
5ccea2dcee475f6da628beb555f6a8c10fd415da1429cf7d0c113b26b3dfff03
Both payments are on their chains and locked to the same secret hash feebde0912e5ae98662174422103ddddc61357d3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5ccea2dcee475f6da628beb555f6a8c10fd415da1429cf7d0c113b26b3dfff03
- MakerPaymentSpent: df8b8f3b09d6c9b8edaa68702dec773de532a1b40175d1685f39779d388e1b38
02939ec0f0196ce497200e2198f1652082d7cd55116a5326fca6c006c98e4a15
Both payments are on their chains and locked to the same secret hash feebde0912e5ae98662174422103ddddc61357d3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 46b2823e6ef3b517f2ce73fb5273840340a06170c70b24762eee974c7c132cc0
- TakerPaymentSent · TakerPaymentReceived: 02939ec0f0196ce497200e2198f1652082d7cd55116a5326fca6c006c98e4a15
- TakerPaymentSpent: a5fd9734ed15f006173e2330c0862fabf3e7c92a816368240aec97de57571b10
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.