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.
00d23f138be5a4b0e6322deb0c33a5a022e16011b65822b369850b4ee4c9e9bc
Both payments are on their chains and locked to the same secret hash 5597b79d7798d24e240667685471b0e1f8480f70, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 00d23f138be5a4b0e6322deb0c33a5a022e16011b65822b369850b4ee4c9e9bc
- MakerPaymentSpent: b9d558736edd6232305d8269fc2c3ed46391af52b842494f990c868cbd391919
66d92e1aa67807090652abab18c6fa02995db244972db66add3c2d632badaedd
Both payments are on their chains and locked to the same secret hash 5597b79d7798d24e240667685471b0e1f8480f70, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0dba5d8044a2ab612a5803aa8dc8c0f70bcab73434fe4605b5f5727e2c71c4ea
- TakerPaymentSent · TakerPaymentReceived: 66d92e1aa67807090652abab18c6fa02995db244972db66add3c2d632badaedd
- TakerPaymentSpent: 5ce97e06dd251500d33f33597aa5a8451e66538f38238ad4954911bfa30342d5
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.