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.
d3a1f136f883145300bcdfc709a1b828663a4d14d26cbd6073ac216ca56a4c33
Both payments are on their chains and locked to the same secret hash 36ab45b1ddad767dc8e66f4327a73e8e257ae035, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d3a1f136f883145300bcdfc709a1b828663a4d14d26cbd6073ac216ca56a4c33
- MakerPaymentSpent: 967191705e0aa51cd00ad83db18eefac08523ba0453fcae43eeecf68f8d709de
3005f5fb810983af0af3af958cf1dbf785302334f58b00426ee36b17d97dcae7
Both payments are on their chains and locked to the same secret hash 36ab45b1ddad767dc8e66f4327a73e8e257ae035, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a981d2a78b73a5d5798c44baa5b34ee05c65ab6108b60670749320ee97141be8
- TakerPaymentSent · TakerPaymentReceived: 3005f5fb810983af0af3af958cf1dbf785302334f58b00426ee36b17d97dcae7
- TakerPaymentSpent: 3057378c3cccf23473b214ed2b0ffd19c8108e9952fa7011992736e554f1278e
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.