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.
d6923bd2abcfcf1e007718820825ef637e35b72543c6935fbc33ba4507095d97
Both payments are on their chains and locked to the same secret hash 7e3e1d558a8efa31447056045fee6e13c3d3badf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d6923bd2abcfcf1e007718820825ef637e35b72543c6935fbc33ba4507095d97
- MakerPaymentSpent: 19878a05ee945d371301984b7954a18a40444f36a15ca5c510b3db5fad3b1031
c5f24eee7678ea119c0920e4d0527e7e60dd09f209058f6329a69adfa1408655
Both payments are on their chains and locked to the same secret hash 7e3e1d558a8efa31447056045fee6e13c3d3badf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 388a99f5614e85ae8d8ceff231e97b5083474ab1f7341aa06e44192bb15dd5fe
- TakerPaymentReceived · TakerPaymentSent: c5f24eee7678ea119c0920e4d0527e7e60dd09f209058f6329a69adfa1408655
- TakerPaymentSpent: 854ee2f0e91ee18c4933bdf6d5fb686c4e702dbccc26c66b514c2330b04006d7
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.