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.
5eaa2999c364b0eb98057deb48012f150312ab90ccddaca9548683264d38a7d1
Both payments are on their chains and locked to the same secret hash 058f92ebea56ab70a93158a67d6947c3ad3f5aab, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5eaa2999c364b0eb98057deb48012f150312ab90ccddaca9548683264d38a7d1
- MakerPaymentSpent: ecb0e494a70fb4dd358e1f5860aa5fdffcc02e438b8400cbab6579c78b59961e
d2aab605554099999e1dce1f08b550af24f401d196871860e63851df6a1b554a
Both payments are on their chains and locked to the same secret hash 058f92ebea56ab70a93158a67d6947c3ad3f5aab, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0701bcff80e90745cfade4ad8c2d5923624db8e972c280ac75d7eda567c7088c
- TakerPaymentSent · TakerPaymentReceived: d2aab605554099999e1dce1f08b550af24f401d196871860e63851df6a1b554a
- TakerPaymentSpent: e1766b17a2e1c0f920461932cf885bad1f22366690244ed6245bccd12bcb495c
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.