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.
5c83763d58141369e2e339592edfc798d55aaf28e397568bc6d298b42827faf8
Both payments are on their chains and locked to the same secret hash 806392267555be6188d3131fb0b3840f9d00a55f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5c83763d58141369e2e339592edfc798d55aaf28e397568bc6d298b42827faf8
- MakerPaymentSpent: 452ee7fe3d2691193ae30fc9d1be6a4d1d2dbefcffe88f2763bbd3da11c36ee7
2bc3c2c3380a94ca2fad4eafdee60eff07ea6fda1242c01078b556d227a2a03c
Both payments are on their chains and locked to the same secret hash 806392267555be6188d3131fb0b3840f9d00a55f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 48f5b64236e559820611bf55c21492f9a22b075caec7d5fc4249478234f9f2f5
- TakerPaymentSent · TakerPaymentReceived: 2bc3c2c3380a94ca2fad4eafdee60eff07ea6fda1242c01078b556d227a2a03c
- TakerPaymentSpent: 0f803e3c56ec784ae1b98b65bed59fe965bf838133762bc628f239b9c1b44aa8
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.