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.
e9f0d3a5faf9b1d1462392cd6ed6b2a8939e38b6e8e52ed00d48368f8e7ef02c
Both payments are on their chains and locked to the same secret hash ea99fd2a7ab3c547d1a34ee0c8aa7e75a7716b06, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e9f0d3a5faf9b1d1462392cd6ed6b2a8939e38b6e8e52ed00d48368f8e7ef02c
- MakerPaymentSpent: 125479b6349c82160ec753272e5bc142486df99622afb07a4687b6a4bb0d2781
d794226fb5b893db2586a5d1b76aa260a9a1676c285b88af8810b1de768be0b4
Both payments are on their chains and locked to the same secret hash ea99fd2a7ab3c547d1a34ee0c8aa7e75a7716b06, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b7fc2e0b412fb697bf801091b8962253ae711b1db63121edb2a13bc538d24b10
- TakerPaymentSent · TakerPaymentReceived: d794226fb5b893db2586a5d1b76aa260a9a1676c285b88af8810b1de768be0b4
- TakerPaymentSpent: a378c8ad35c862714ffe8e83a68f578c7de625707eed660f7510f4e03ff4b0f6
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.