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.
21513443489c773414c69194f2a474f90cf8abac2eafe86ff011f74de1b8ec2f
Both payments are on their chains and locked to the same secret hash fb3496fa0ee5113ccfde1cf31792a177a7605e51, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 21513443489c773414c69194f2a474f90cf8abac2eafe86ff011f74de1b8ec2f
- MakerPaymentSpent: cec84961bc96f3bc2df3b4b75e68cdab9e2ce25deaec3889789810b51d2e15fc
f8a91576e774a7b0d8e0d82afab2dc5b18d5c72b1eee5301b5ba2e199fa60e51
Both payments are on their chains and locked to the same secret hash fb3496fa0ee5113ccfde1cf31792a177a7605e51, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea993ffb9e043a5d421cc76acbb1dd698b387a6c6048b46746c1696ced72d28f
- TakerPaymentSent · TakerPaymentReceived: f8a91576e774a7b0d8e0d82afab2dc5b18d5c72b1eee5301b5ba2e199fa60e51
- TakerPaymentSpent: 5a411ce8deb371cc6252e6d36360ef5cfd7616e38ce1d66db9ca14144ed6527b
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.