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.
250a80c3fb7e8d8343995df34073d336e2aaf119ec653750106576b233a9514f
Both payments are on their chains and locked to the same secret hash b94a03abf88d4f5550525b2691efb3bc4e3fd338, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 250a80c3fb7e8d8343995df34073d336e2aaf119ec653750106576b233a9514f
- MakerPaymentSpent: b1d0673242886d8861c02bacf90e0a08a27c71389697fcdfd95d4574d235b1ed
9370b96526f6d1d7409bd5862edbf1ad71483c6cd215fa535410e4ed32d28076
Both payments are on their chains and locked to the same secret hash b94a03abf88d4f5550525b2691efb3bc4e3fd338, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4b4e271d310a5d2f9c97449eab1533c64e5911979ee44c091feea8d417eac9ed
- TakerPaymentSent · TakerPaymentReceived: 9370b96526f6d1d7409bd5862edbf1ad71483c6cd215fa535410e4ed32d28076
- TakerPaymentSpent: 81827e37e3a649486ab6be40983813303769a74f16cd0e3db339cb9f35311a33
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.