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.
906f2b951f832b706bae2884428cfb42ca5051994468535f59364a90dc3fbed1
Both payments are on their chains and locked to the same secret hash ceef9158857751000d9272eb64d537361b634eeb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 906f2b951f832b706bae2884428cfb42ca5051994468535f59364a90dc3fbed1
887266e6d5a1bdbe8862ed76e7d0cfeb74720b7f6e7ad809c78f4eb6e97e5b2e
Both payments are on their chains and locked to the same secret hash ceef9158857751000d9272eb64d537361b634eeb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 7c10834e6b7a6580a4f8e490ae48497cf3572c1ba32ab7890bd736e49dc7405e
- TakerPaymentReceived: 887266e6d5a1bdbe8862ed76e7d0cfeb74720b7f6e7ad809c78f4eb6e97e5b2e
- TakerPaymentSpent: f999c4d5118d940c820a0a35b07226669c8eba558d98fd7eaf966c42f4f19e97
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.