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.
901c5b81b294b0b2f14681dea767581acc651c9ca4ebba3dc1d381db7b7b373e
Both payments are on their chains and locked to the same secret hash 61f45e1e8f9b288ca9627a0c4e8df3092a926422, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 901c5b81b294b0b2f14681dea767581acc651c9ca4ebba3dc1d381db7b7b373e
- MakerPaymentSpent: 6631819883c6bb9ec103a1baf449a9392215c0c2dfd27ff38f18f2a790ee8383
3c915113c18fae0cae5c1c6bb0fe0f6a7423183e7649a4ef2305d2aefed2f159
Both payments are on their chains and locked to the same secret hash 61f45e1e8f9b288ca9627a0c4e8df3092a926422, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1e1a2f5dbc4491ddd8c26df97236c1251170025c09bf4d5fcc5879352e497730
- TakerPaymentSent · TakerPaymentReceived: 3c915113c18fae0cae5c1c6bb0fe0f6a7423183e7649a4ef2305d2aefed2f159
- TakerPaymentSpent: cf4d32f23aaa3300c6baad03937a0a2fd5803aa5819b0020b550e2311ad51d8f
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.