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.
565d6fed4d5bea7e0e51ae97d26f981b227095d1dfe08794e52f652ff90d8ce6
Both payments are on their chains and locked to the same secret hash 6354c6475f3658fea6a437a50139731fe67d4698, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 565d6fed4d5bea7e0e51ae97d26f981b227095d1dfe08794e52f652ff90d8ce6
- MakerPaymentSpent: 05c20252e3e526696b5aa30ecaa78595517bf3d2ca2feea9eb1dcf7a5db0db05
16dda1516bfa1d99ed3b01c099228511fd7a160f645874e29f0ea0540ce8e824
Both payments are on their chains and locked to the same secret hash 6354c6475f3658fea6a437a50139731fe67d4698, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 055c1ba180be1841b2fc2e8df12837803898cb4281045cc48ef09f92ecbc3509
- TakerPaymentSent · TakerPaymentReceived: 16dda1516bfa1d99ed3b01c099228511fd7a160f645874e29f0ea0540ce8e824
- TakerPaymentSpent: c8d7d4ac6d8183de8886ef03adf65696a314aae5787996289e2afd1d50787e9d
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.