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.
f65fa1b2e6a0946d6dc3b3eec26ea54da09ffb64a60a4fd5030335f852fb7d2a
Both payments are on their chains and locked to the same secret hash 536de8a291aa835e369120ae7e12c0e9be9f2b5a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f65fa1b2e6a0946d6dc3b3eec26ea54da09ffb64a60a4fd5030335f852fb7d2a
- MakerPaymentSpent: 61646f286619eee4edabdaae9f4fa822e00dea415a1b0c67ebf4988feab42861
939ec2b20e655bcd72200722937a45318cc82c79df765435a2605004b6ba939a
Both payments are on their chains and locked to the same secret hash 536de8a291aa835e369120ae7e12c0e9be9f2b5a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3fd9d6f0d32c28767c4fb1bedebe19c46039cb44a0a095d0f7f63651e12ce309
- TakerPaymentSent · TakerPaymentReceived: 939ec2b20e655bcd72200722937a45318cc82c79df765435a2605004b6ba939a
- TakerPaymentSpent: 054b5c123310788d067df8cfd5db80236a7693bb0782d803746640aa6a66712f
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 defistats-gleec.