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.
f0bc30089ac7c9a46b710ae8a7deddd90ecb281afe727d4ae5936f530b7bbfbe
Both payments are on their chains and locked to the same secret hash c875f0af09ac32e3c33d568654530c3f5d33487f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f0bc30089ac7c9a46b710ae8a7deddd90ecb281afe727d4ae5936f530b7bbfbe
- MakerPaymentSpent: 66a89bad29f1c4105b3b5b932a9ed859ace0dcd8174640737657f3206d7de2d3
d4d1373e3311355c910b24259df1958444a2d623eb9ae5408ec5653e7d39d8b8
Both payments are on their chains and locked to the same secret hash c875f0af09ac32e3c33d568654530c3f5d33487f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 44e2953407d2b099903f9fc8db460d91ee473cafcf2cf6a5fd78f8d34195d631
- TakerPaymentSent · TakerPaymentReceived: d4d1373e3311355c910b24259df1958444a2d623eb9ae5408ec5653e7d39d8b8
- TakerPaymentSpent: d8cce0a842062e4c64173801d5db268126b2853660686294a48f7021052cd39e
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.