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.
9626c4d314cc2f4109688fd457aa5430a982cd0b2365f2f041d514eba29db508
Both payments are on their chains and locked to the same secret hash 28e00458412d175a68a99eb9638f0a47b4b8f644, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9626c4d314cc2f4109688fd457aa5430a982cd0b2365f2f041d514eba29db508
- MakerPaymentSpent: 0434d8d5c98cf8bec977f2c7dd4639483b7b1547f222ff55a2f791c6415d91c4
98f271bb9d9a6b7383665a69a3775dae5fb18a68d09f25f255fcfa36f99b4223
Both payments are on their chains and locked to the same secret hash 28e00458412d175a68a99eb9638f0a47b4b8f644, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f61a36bfb6669f24df8d0c89526c5d1a7d6a392fdefff1cc08568f8b0a8ff519
- TakerPaymentSent · TakerPaymentReceived: 98f271bb9d9a6b7383665a69a3775dae5fb18a68d09f25f255fcfa36f99b4223
- TakerPaymentSpent: 73769af5033627f1e3ce065bb3c9f6b14c06c79aad6144b54f3ed912e325132a
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.