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.
45ba48fad9563bc37aa29110b6607a2b1e4b77c38e8a3289a7532c66abe0a55f
Both payments are on their chains and locked to the same secret hash e22338c073311217b749cf199da6d5a4761dc49f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 45ba48fad9563bc37aa29110b6607a2b1e4b77c38e8a3289a7532c66abe0a55f
- MakerPaymentSpent: 0b2be0412742e725068e5d55462a474b7c10032300db94c0a566593754e6269a
013dfdbfb627410cfa484d3ba41d8d8a9441470bcfe04cd60bf73a7b48a12159
Both payments are on their chains and locked to the same secret hash e22338c073311217b749cf199da6d5a4761dc49f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 55700db147aca142e9583abd8d63f5f59b0e55363b36b695bfd8bb528478cc70
- TakerPaymentSent · TakerPaymentReceived: 013dfdbfb627410cfa484d3ba41d8d8a9441470bcfe04cd60bf73a7b48a12159
- TakerPaymentSpent: 7973861212ebf5e424adc1362a651c36e4b5ac9b4ffebd92bb22785db66c9e67
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.