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.
dd373859c217839b53901ce668b08ec3367c5c95e0b529c28cdba66bc596a6c3
Both payments are on their chains and locked to the same secret hash 2d286665d149a790e24bec23c45f9bb2aab76db0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: dd373859c217839b53901ce668b08ec3367c5c95e0b529c28cdba66bc596a6c3
- MakerPaymentSpent: 03ad4aae2fd2c77f5e128516e9fc0595c8f6151b3e33157e2d9f5066279c2097
87d80f11e88fe2037d00abe3ca339e002b998cb8332f7d872d9fe82ff3d8a836
Both payments are on their chains and locked to the same secret hash 2d286665d149a790e24bec23c45f9bb2aab76db0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 842367cfe850868eb2270e8c1e5c69cde6cf025687e3d9ed66df60d0b1ff4636
- TakerPaymentSent · TakerPaymentReceived: 87d80f11e88fe2037d00abe3ca339e002b998cb8332f7d872d9fe82ff3d8a836
- TakerPaymentSpent: c36ac85188a22d737d890c98b6fa50ea6463095c29d77c679c4323d9263e22b4
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.