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.
e846d03f36ded8325c13af68c966cd53a7bf6c219d68c5ade3bfa763c4243dc3
Both payments are on their chains and locked to the same secret hash ffff64d06da0f95cddb97f5229227f52abcb2f69, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e846d03f36ded8325c13af68c966cd53a7bf6c219d68c5ade3bfa763c4243dc3
- MakerPaymentSpent: a38fd6d11791f68aa6c3c0bba785353533596dd84c7cc9bf2dff5376ae89cdb9
6a5c52ab1d5c574c1e93d1797deb5907f6e207864432def74f59a4874ef2b654
Both payments are on their chains and locked to the same secret hash ffff64d06da0f95cddb97f5229227f52abcb2f69, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a7efa61b28f65e380be5b081b9f8e8d05bab52561cab78995315e3a02c44b29d
- TakerPaymentSent · TakerPaymentReceived: 6a5c52ab1d5c574c1e93d1797deb5907f6e207864432def74f59a4874ef2b654
- TakerPaymentSpent: 719b6ae089c8c55a3c129ce8e14ef80b6f3316f3b8ea77b9d13d161589a8b78d
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.