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.
d2d1e3abe71bf85744c7307007a7f9fbc2bcf3113a601970e5c8941c776fb793
Both payments are on their chains and locked to the same secret hash c9b7276888c622b8993039eb247943032d3a98f0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d2d1e3abe71bf85744c7307007a7f9fbc2bcf3113a601970e5c8941c776fb793
- MakerPaymentSpent: 7a05da026accc34c61cc27aad0aa814d82e7c7c501c541d85c053a53fa845e02
ff75217983b723db895323013c8b660116558bf4136b325d951909e43b73aaf3
Both payments are on their chains and locked to the same secret hash c9b7276888c622b8993039eb247943032d3a98f0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 28709c51b8f0cb64be33379a3292e3760e603ee0f9f0af0de76daae09a7b4006
- TakerPaymentSent · TakerPaymentReceived: ff75217983b723db895323013c8b660116558bf4136b325d951909e43b73aaf3
- TakerPaymentSpent: 6406eab744cbd5d26901200c8b5d8cf266c0783f6ebd47d35d5a808c91f73d6f
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.