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.
76dd30290edcaa123326ae4e851180553e2db6c203935668eab1472f55e2b912
Both payments are on their chains and locked to the same secret hash b2e531c9d9a4ef55b8116934ed4fba8cd982c442, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 76dd30290edcaa123326ae4e851180553e2db6c203935668eab1472f55e2b912
- MakerPaymentSpent: ad96abede67bf3dc2b58b46501df2bb7aeab3b96c1614d794f11392fba27065d
959a887f8b6238e1740998f36c526852e939425c449f76ffb4eb46a05c027412
Both payments are on their chains and locked to the same secret hash b2e531c9d9a4ef55b8116934ed4fba8cd982c442, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 24ae1bd9d637d9174e4231be01c12942441cbdb15c01adca8ed651dc68988b76
- TakerPaymentSent · TakerPaymentReceived: 959a887f8b6238e1740998f36c526852e939425c449f76ffb4eb46a05c027412
- TakerPaymentSpent: 65fff2495c957e7e26af1d70a08f766d588318107e5ebd650e2697a11a74a8e6
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.