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.
c3c4e2609e330ecceb5eecfd264778fc74fb489534c318c6d65ae45ed123900b
Both payments are on their chains and locked to the same secret hash 205622329ef2377a708be956ed76f2a819d52c43, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c3c4e2609e330ecceb5eecfd264778fc74fb489534c318c6d65ae45ed123900b
- MakerPaymentSpent: 42b5a13719f38f9d268bd5be9719131f159d69e543e1181c269b95b2533a8134
da63b5b9108bcc56141a5947eee8ebfacc81785565c0c000f3641be576b5f938
Both payments are on their chains and locked to the same secret hash 205622329ef2377a708be956ed76f2a819d52c43, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 07afec59e73134976643164f0dba3b0b67f5631eccb0f85a97e3397cf6c747ad
- TakerPaymentSent · TakerPaymentReceived: da63b5b9108bcc56141a5947eee8ebfacc81785565c0c000f3641be576b5f938
- TakerPaymentSpent: d0f925feb8a809359793adc70dd4745fcff44d79eb3604397ef2b47f8f044efa
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.