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.
2156e2205074718dd9e7b1004d2c868e08e9065de28c488c6e16e21de5509b63
Both payments are on their chains and locked to the same secret hash 7d75034cf7974e84e0d3f32fdd4546c95dc8af6d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2156e2205074718dd9e7b1004d2c868e08e9065de28c488c6e16e21de5509b63
- MakerPaymentSpent: f36dba3f9de185ffe45cc38962b724152327165a0709e9b37485f31882c29a6a
584936f572888f7e0f4317cc182bf8538c61ee8ffc7192de10a119682979a57d
Both payments are on their chains and locked to the same secret hash 7d75034cf7974e84e0d3f32fdd4546c95dc8af6d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6d58d1f2e07c1a8df85ae1d38daec1bce76600618856db9c0826f029bd3da78f
- TakerPaymentSent · TakerPaymentReceived: 584936f572888f7e0f4317cc182bf8538c61ee8ffc7192de10a119682979a57d
- TakerPaymentSpent: 52ac673146e7cc46fedcbc76e8d22b63acd16e6a2a79794aab84e46cfd065377
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.