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.
61d2ca04768ec615828519003feff0b4b4f9a1eb8c6aa898173082921b1e9a1f
Both payments are on their chains and locked to the same secret hash 6c3c513f9cf100955ff16a3b8b4a6c79d9a94c74, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 61d2ca04768ec615828519003feff0b4b4f9a1eb8c6aa898173082921b1e9a1f
- MakerPaymentSpent: bf68de336760ffa309080357f0da46f64d1a9768b8ab5f5470d2ff453da400d5
1bd536dbcac90fbfa71a6f30b32f98ee0809d6bd41da2422b1ca932f4d64925b
Both payments are on their chains and locked to the same secret hash 6c3c513f9cf100955ff16a3b8b4a6c79d9a94c74, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b2f45563226bb41dc0c153b19e1623d415f698715b4357a0056f56b8c286aa99
- TakerPaymentSent · TakerPaymentReceived: 1bd536dbcac90fbfa71a6f30b32f98ee0809d6bd41da2422b1ca932f4d64925b
- TakerPaymentSpent: c4b7f5dd54790c4f26f3eb6c55e6a77fc2f02b1fe4d48f83d7d7d0c2735ce1fe
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.