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.
cc0b86d4075c073a671400faec6f1307f2cef9364a30f9b0588fc44dbab48fad
Both payments are on their chains and locked to the same secret hash 696dc06567284f986f1ee10fb0d7a9c1f109edfd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: cc0b86d4075c073a671400faec6f1307f2cef9364a30f9b0588fc44dbab48fad
- MakerPaymentSpent: f899c7a41888aed588606d12b0b07b86cba2a08bdc79d62f70bfa080b2fca8f5
bfff53ab1b2abdc7a9baa3c48a7c23f30824bc8e4aef74d1b179ea80b2021333
Both payments are on their chains and locked to the same secret hash 696dc06567284f986f1ee10fb0d7a9c1f109edfd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 17dba67d92f2d7ddafdcc22da65d7462c38549b79a7e2258f4e06d4182014075
- TakerPaymentSent · TakerPaymentReceived: bfff53ab1b2abdc7a9baa3c48a7c23f30824bc8e4aef74d1b179ea80b2021333
- TakerPaymentSpent: e773de024146c2a8e7280830bcac5b0340f1f5829c5435661b7ac3d476a33fc6
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.