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.
7e0a1d3b5fd2b42b52ec7d4c674d04930ded80d9914b7b373bb7e656d07fdaaf
Both payments are on their chains and locked to the same secret hash 9f097fc1c58e19245d261dfa19dfa13d5d302785, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7e0a1d3b5fd2b42b52ec7d4c674d04930ded80d9914b7b373bb7e656d07fdaaf
- MakerPaymentSpent: dd2707fefcc7401dc5e3fa76e43ae7e2a3c84a48f8578e56729d3e0a6734c8c3
3400aef0ef370bbfd0f66a5059e34a19515da64663a5b0957109a8219a423625
Both payments are on their chains and locked to the same secret hash 9f097fc1c58e19245d261dfa19dfa13d5d302785, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bb65cb77ca004186291f28c56784bc6870b3b18be7c9b0c90af3eab4871166c5
- TakerPaymentSent · TakerPaymentReceived: 3400aef0ef370bbfd0f66a5059e34a19515da64663a5b0957109a8219a423625
- TakerPaymentSpent: c7ad8581c583529ac5f7b059df1fb0192e65d739789091ad7ead7fa7904d74b1
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.