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.
a489a481bf360f42b30fddb9531b883a677d402682ff4547cd42986c983d3308
Both payments are on their chains and locked to the same secret hash 6c10ba34853d0c782f6f47244338806275b2ada8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: a489a481bf360f42b30fddb9531b883a677d402682ff4547cd42986c983d3308
- MakerPaymentSpent: 0929a8b21bb4c5b97c69f0e79dc01f35d51389eee34b3eb5cd0b1741a9a55870
69fe527a89d1d3c0601bdee1051910421e0fe6966a7e0e41ad50af637efb322c
Both payments are on their chains and locked to the same secret hash 6c10ba34853d0c782f6f47244338806275b2ada8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 79a3e4e77d5097d6dd83400392a48da0e164e8b71a9c3f3e3239df67694cf6f0
- TakerPaymentSent · TakerPaymentReceived: 69fe527a89d1d3c0601bdee1051910421e0fe6966a7e0e41ad50af637efb322c
- TakerPaymentSpent: 25fb1627f77162f6f05e48927fb758494fa627a64862d90e313c83998e51eaa5
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.