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.
a8fa59a961f680f48f4cfd7368fe65d9461aec8d0a11f83e7c9e559595497854
Both payments are on their chains and locked to the same secret hash d73ebd0b218a05a9bb00867b717123c7da6b5f0e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a8fa59a961f680f48f4cfd7368fe65d9461aec8d0a11f83e7c9e559595497854
- MakerPaymentSpent: 1e90cf55771658f6de386b33ad1b36dab83a0b6ad63c9db6d25e0e9f1e825d9c
80df639e6ca46720e7521135f7ca2b8c99236d464cfd21bbc902fe7d4cdc10a7
Both payments are on their chains and locked to the same secret hash d73ebd0b218a05a9bb00867b717123c7da6b5f0e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a14694e689348de449ef403538614101c4eb14eee9a6a8d7cbdc9a6c78c3108a
- TakerPaymentSent · TakerPaymentReceived: 80df639e6ca46720e7521135f7ca2b8c99236d464cfd21bbc902fe7d4cdc10a7
- TakerPaymentSpent: 50d8ed5bdb166c67e1749851fc076faff2150d290b8bbe787ff2f7356e40f1a6
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.