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.
8fa26de31d32a5b72441c1a481800da362c9167dc4c491e5bc6a997a6412eba0
Both payments are on their chains and locked to the same secret hash db31b487ffeb9c580b2ee2b5b425851730bcf3e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8fa26de31d32a5b72441c1a481800da362c9167dc4c491e5bc6a997a6412eba0
- MakerPaymentSpent: 7fd626073d9e83c5535cbc8912654e3ece07e66b6a910e7d65ec14f18f7d29ac
c0eed497cab03bf09199287e86c3e0ebc968882b8959a466a5ac63d95aa328c5
Both payments are on their chains and locked to the same secret hash db31b487ffeb9c580b2ee2b5b425851730bcf3e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3dcc468fe79d1b94cc077be1f8f9961a8d4e829caf29b72c838aa6d6837b0a3e
- TakerPaymentSent · TakerPaymentReceived: c0eed497cab03bf09199287e86c3e0ebc968882b8959a466a5ac63d95aa328c5
- TakerPaymentSpent: 2a192c3567e4a84ef4f6ce2aa64db82a4a983c69c4d2ba3a98f7ba98a2578e86
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.