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.
0aa0dcc5e6aae9f8ff94871881e0cd28be3e9ebd5345dfb1dbff8bcb49f61ffa
Both payments are on their chains and locked to the same secret hash 96659987d7ced7840bebb53c5a320943c7366cf1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0aa0dcc5e6aae9f8ff94871881e0cd28be3e9ebd5345dfb1dbff8bcb49f61ffa
- MakerPaymentSpent: ca508cd6f7d6e9d5b87c011d06f3d5f910f0bbcd97e65e189eb4a2138cf9a074
c7f6a3f94218576d455f573adcef9ea37d5023ca1d53a97e69453274ba0935b4
Both payments are on their chains and locked to the same secret hash 96659987d7ced7840bebb53c5a320943c7366cf1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a75360b91f9ef995e4989b863b80624ea08467a89912e3f50e878e35a260272f
- TakerPaymentSent · TakerPaymentReceived: c7f6a3f94218576d455f573adcef9ea37d5023ca1d53a97e69453274ba0935b4
- TakerPaymentSpent: 419fa923ac8fdab88fb0c684f5da0adea0e6527d2a7c5cd3929308869597fcf0
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.