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.
ad8e77b57bedb338421bc8e0d7f825834729654958d2370fe41137247cb596a8
Both payments are on their chains and locked to the same secret hash 4283058634303ce97617ddb7dba21d6c2e9f4e68, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ad8e77b57bedb338421bc8e0d7f825834729654958d2370fe41137247cb596a8
- MakerPaymentSpent: b0692cfa65070c40ba851f5116c342681c48fb944ef0e6a572fba482336088c8
5056ff2da6e9313c1124b82ac46c7d03736b2c03267ff3298a1b45130c77d4f7
Both payments are on their chains and locked to the same secret hash 4283058634303ce97617ddb7dba21d6c2e9f4e68, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f9f0b2dddd361aceac4acaf7651d971e57954d84fcf81431121baa2331ee670d
- TakerPaymentSent · TakerPaymentReceived: 5056ff2da6e9313c1124b82ac46c7d03736b2c03267ff3298a1b45130c77d4f7
- TakerPaymentSpent: 556e723fdb99a8c8d6e8237b739a2638844fc4d09d50a90c6c2b254cbe2ce5ba
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.