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.
bf49042a5b3fbea9d44485e22d8e50956cbc0a370d107da86946328ce60eb56d
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: bf49042a5b3fbea9d44485e22d8e50956cbc0a370d107da86946328ce60eb56d
- MakerPaymentSpent: c4445969bc7333160dec82d67f8caa29f2b86b6af334f790ae92009d84f4b9dc
8796b2c06d750a4c017d62cde40bbd4dead98b5ba67f1b00e60eecadf79821b8
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: e2cd73b1b33b0ef7c56581c2895bf7c848c231c82256c2f658215da140eb1374
- TakerPaymentSent · TakerPaymentReceived: 8796b2c06d750a4c017d62cde40bbd4dead98b5ba67f1b00e60eecadf79821b8
- TakerPaymentSpent: 16cd1100b901f1e08bcc534bd705007b74827f7cea545182dd7c2357630c200a
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.