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.
e6996e6482b0de5b6e514caba66f77dcbb521689735625848cc7267da5c47db4
Both payments are on their chains and locked to the same secret hash 2d805c809eba9e72c5511385dbfff3a74c1f0b9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e6996e6482b0de5b6e514caba66f77dcbb521689735625848cc7267da5c47db4
- MakerPaymentSpent: 2f9fe0e4f6bc5518e66a728f38e444196c7de4c0bfe86de8546f283ef92a364f
fd2a4b940fcf1f306634f094de6943e163ce222a57dbc293b5bb4282abbbc894
Both payments are on their chains and locked to the same secret hash 2d805c809eba9e72c5511385dbfff3a74c1f0b9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b12e8dac069a844c03e29bb2fa648f5fc7a316f3a5d45f37cf12760361436aea
- TakerPaymentSent · TakerPaymentReceived: fd2a4b940fcf1f306634f094de6943e163ce222a57dbc293b5bb4282abbbc894
- TakerPaymentSpent: e760c384d4a593b3c6148ce516f6b09ce1f1b7c0a324f0bcdad7380de7b991cd
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.