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.
7d58479436d22fbbe4ead4e0d4ee763c98f801f213a704f1a56113e4ea8eccf0
Both payments are on their chains and locked to the same secret hash bf79f203c8f7f64da82b641b9d14a98c37cd8622, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7d58479436d22fbbe4ead4e0d4ee763c98f801f213a704f1a56113e4ea8eccf0
- MakerPaymentSpent: eecaa891e6e8b3d564ed43ddce212437fc3c980961809a40f4c94bb9481fdc43
016dea134a57cd0d1f8df7e849495e3f002e7e0db5f23d3b0ae06ad81c55edc5
Both payments are on their chains and locked to the same secret hash bf79f203c8f7f64da82b641b9d14a98c37cd8622, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 99860af09b5d351cc6b85e201132161a26cee5f490eee8b28534a34103fffd43
- TakerPaymentSent · TakerPaymentReceived: 016dea134a57cd0d1f8df7e849495e3f002e7e0db5f23d3b0ae06ad81c55edc5
- TakerPaymentSpent: 65517ee1cc22d9cc70e61ed0b6bb68e92d0d817af3f19599cbdeaa409c407883
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.