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.
The swap stopped at TakerPaymentWaitForSpendFailed.
Timed out waiting for taker payment spend, wait_until 1792468714, now 1792471859
Recorded by the swap's own protocol log, which is the only source that knows: the aggregator reports failed and completed swaps identically. Nothing changed hands, so it sets no reference price.
a16605b3cbe3dd410f5d83e6b3083b46d2ce6436b849300632c2e3e2312a8cd9
Both payments are on their chains and locked to the same secret hash 69e7aea1566d19d2832607151818f17c1202e376, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: a16605b3cbe3dd410f5d83e6b3083b46d2ce6436b849300632c2e3e2312a8cd9
e2e1340cd2d12ae4f78524a209b31d8ad120b136fd9ff051187fa318499833cd
Both payments are on their chains and locked to the same secret hash 69e7aea1566d19d2832607151818f17c1202e376, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: a56c3825c9f5b819e5af7596035dfbebc402ab9d3a5edb491bdfa600751b2c1d
- TakerPaymentReceived: e2e1340cd2d12ae4f78524a209b31d8ad120b136fd9ff051187fa318499833cd
- TakerPaymentSpent: be451ade8ea1606aec7fc59cb31c03f6e8807214a0ac7247677135428998b376
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.