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.
f9577bd89087967ef43f402974151e93bd329e2e746c56592e75d1217229a536
Both payments are on their chains and locked to the same secret hash 67c8df917457d84430a797144d505bf648a2bb73, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f9577bd89087967ef43f402974151e93bd329e2e746c56592e75d1217229a536
- MakerPaymentSpent: 1d971f724b336c572e5af5a95a496fe5e2430e5b2a5aa639b269659e1572b59a
42a335f0761586c92262ec598723f6e3b100e4afb24a5a747974fa293a004312
Both payments are on their chains and locked to the same secret hash 67c8df917457d84430a797144d505bf648a2bb73, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 108ea4c8ae98f4e3ae0863baeadf1c18b2e62a48b13dfad7c104af12acef627d
- TakerPaymentSent · TakerPaymentReceived: 42a335f0761586c92262ec598723f6e3b100e4afb24a5a747974fa293a004312
- TakerPaymentSpent: 96618dbacba3a21531a46106e11a241cf26353eef54678b1cb77737463882f64
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.