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.
b342121833be5b3d2fd64d770f793dede3543bef8fc847c2ae230b48baba0d28
Both payments are on their chains and locked to the same secret hash 561995ed51738f7c3e68ca1c2933b5e97535ff5a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b342121833be5b3d2fd64d770f793dede3543bef8fc847c2ae230b48baba0d28
- MakerPaymentSpent: 705cd3e55fe7518c79fc4a72cd24ba58ad6af48235c4670c68b7476adf5f82d7
199fbbf9748bac3ab1795bdcff0f1da23b3061ec3348404635a13c82d2eb2591
Both payments are on their chains and locked to the same secret hash 561995ed51738f7c3e68ca1c2933b5e97535ff5a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bc68b37c367748bf626310983c6912d56e49eb1a62208b7d5da239820dcd9cd1
- TakerPaymentSent · TakerPaymentReceived: 199fbbf9748bac3ab1795bdcff0f1da23b3061ec3348404635a13c82d2eb2591
- TakerPaymentSpent: 3baa228f87b8af07483b523dd9e4250087c236a9b78811bb4a610a63cde416fc
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.