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.
e0f6a8a68993b7c47ea1fe58d20bc14754d071ec45884ecb3acba85a8d528818
Both payments are on their chains and locked to the same secret hash a2fbc952a9dafb62ce922af1174d8246ebd24d8a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e0f6a8a68993b7c47ea1fe58d20bc14754d071ec45884ecb3acba85a8d528818
- MakerPaymentSpent: 1994238075c9ba4a9d5efaa820edc381db543515e1aff33e401c9ae37e039475
209ebdc1a3370bae32ca4926e7b3ae89212a2f8e6d05a030f90ff415cae23dcc
Both payments are on their chains and locked to the same secret hash a2fbc952a9dafb62ce922af1174d8246ebd24d8a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 034166538b6c2abe99aea9f6763bfa48f0aab72c1eb076b4e0ce07bca582fe4a
- TakerPaymentSent · TakerPaymentReceived: 209ebdc1a3370bae32ca4926e7b3ae89212a2f8e6d05a030f90ff415cae23dcc
- TakerPaymentSpent: 5bd21fc34a09877084b3e2429c53c298b52bb6b950f594fd514cf1cb581b531a
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.