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.
df98d56f48f6fa33b710c696d0fd5175d140bc4692857ab498422d1dff794d95
Both payments are on their chains and locked to the same secret hash 27e7e97dc589044384e423191c40e72bb4784068, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: df98d56f48f6fa33b710c696d0fd5175d140bc4692857ab498422d1dff794d95
- MakerPaymentSpent: 991c8b161d24f6c783617188afb5833215639eb27af9bc4b591eb0f321f506e1
4f383b78bee9849c7607f9aadbf4dc805c609417b30d6e283a59c8b1636c3217
Both payments are on their chains and locked to the same secret hash 27e7e97dc589044384e423191c40e72bb4784068, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 57f523a1276c33d6829efb7eb62b4939e53e9bf7eda1d41d218542b955cf8609
- TakerPaymentSent · TakerPaymentReceived: 4f383b78bee9849c7607f9aadbf4dc805c609417b30d6e283a59c8b1636c3217
- TakerPaymentSpent: 866bd7347f356349104c339625a3971937a42ef547c4ceb0dcdbb75e92e8bef9
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.