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.
f245aa22472af51377c9e9788c08f8e9bacf5cc953cfbf1bd66dbfdef8f01c46
Both payments are on their chains and locked to the same secret hash 2ce1644d2be46b210f13b55108b881609d90b8b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f245aa22472af51377c9e9788c08f8e9bacf5cc953cfbf1bd66dbfdef8f01c46
- MakerPaymentSpent: 3d9d0b8fca02267781697e0e7b5f07ff2f4c94a9647fb13cbeca4480a48694a1
b2dff45cecd9167927b3d20702f063d771d42b889b4a3e23f7d7115e69a8f040
Both payments are on their chains and locked to the same secret hash 2ce1644d2be46b210f13b55108b881609d90b8b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: c03c1b98a24723c5b5526c15dfac540aa0db530bb7bf1d647d128e11298d9af9
- TakerPaymentReceived · TakerPaymentSent: b2dff45cecd9167927b3d20702f063d771d42b889b4a3e23f7d7115e69a8f040
- TakerPaymentSpent: b0534e9e0475e7d0bfa0fe99eadd4a5c19e7a3aa1bc70285d115289b51040894
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.