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.
bd2e6ba201416ef713239b0ff57279f244ff48a06639e65fd79b3e9737502616
Both payments are on their chains and locked to the same secret hash d18841dbf0af1766c948bb1d005b11fbfd342396, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bd2e6ba201416ef713239b0ff57279f244ff48a06639e65fd79b3e9737502616
- MakerPaymentSpent: e5d94f4a9c1b40aa2a55558eb91434dd27bf15db268a505cd7059b389af67825
ceefbb05e8021088cb96aafe78b33340c916b4ffced676bdc2b897e7ada82970
Both payments are on their chains and locked to the same secret hash d18841dbf0af1766c948bb1d005b11fbfd342396, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 98f8ba695886c99480d587b2d8809e76daef1743a901fe464afd6654cdf73b2a
- TakerPaymentReceived · TakerPaymentSent: ceefbb05e8021088cb96aafe78b33340c916b4ffced676bdc2b897e7ada82970
- TakerPaymentSpent: 73d9cb5546847012602be220a6a71997084b4df547a718038eabe3113ac1e352
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.