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.
6192b7e743f92203ed7c960028f46fd2a7133c020e6064097e4a8678d04d86fa
Both payments are on their chains and locked to the same secret hash 053871e85609defea4db74388873f7015f3b92d9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6192b7e743f92203ed7c960028f46fd2a7133c020e6064097e4a8678d04d86fa
- MakerPaymentSpent: fca9a1699eb60cbf4868f7b4877549c67e2d31a20c773816eba708ba9e9c101f
f07212ea392026301fb73a4ed1e48dcf90bb37e83badc06b3619bd06fc8fff0c
Both payments are on their chains and locked to the same secret hash 053871e85609defea4db74388873f7015f3b92d9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3807cf85ec49158d096b893c1c1fb69bc82774671e6de38d9cc8832593cc13ee
- TakerPaymentReceived · TakerPaymentSent: f07212ea392026301fb73a4ed1e48dcf90bb37e83badc06b3619bd06fc8fff0c
- TakerPaymentSpent: 020497f5be7da8e169158a7fa29157ef60ed4c3131500dcfd50d5c0f6b3f8304
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.