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.
4a01d59257765419fed9d9cb4b0ec21ace31e09a58c097dd893dc8dcbdd1646b
Both payments are on their chains and locked to the same secret hash 53aea36e88f97323a6b612907acde38e35089189, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4a01d59257765419fed9d9cb4b0ec21ace31e09a58c097dd893dc8dcbdd1646b
- MakerPaymentSpent: e063c1014429374f17224b68057938f40beedf3f2fd6c22d8c9bddaa8bedddd8
a79d070ac12de642a37b35da4b1caabe437f69c4777fa65f662c2035e2ae8fbf
Both payments are on their chains and locked to the same secret hash 53aea36e88f97323a6b612907acde38e35089189, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 115c1df5a06917688c375370ed18ec21dd576e6a30a7b627ea2bf618bfced9a3
- TakerPaymentSent · TakerPaymentReceived: a79d070ac12de642a37b35da4b1caabe437f69c4777fa65f662c2035e2ae8fbf
- TakerPaymentSpent: 7dc3ca3298dcf87244ac0226995a1daf2e9710fb9733ebec08e10237e6dd43f9
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.