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.
924cf07b7fae9409c089e1f74382ab4706b3af5f2f8025c922f220d727b5ab67
Both payments are on their chains and locked to the same secret hash 84346a2dc25c02a5463ce96440caa952f18ac438, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 924cf07b7fae9409c089e1f74382ab4706b3af5f2f8025c922f220d727b5ab67
d654f0cb6cc7ba3b22acbe64cb26bb4fc57f0bbf45b9b39de593c9be7e2264fe
Both payments are on their chains and locked to the same secret hash 84346a2dc25c02a5463ce96440caa952f18ac438, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: be8d6381ed0876b307accc60d0310a9c8c2895a5cbbb23494525277c78c05b56
- TakerPaymentReceived: d654f0cb6cc7ba3b22acbe64cb26bb4fc57f0bbf45b9b39de593c9be7e2264fe
- TakerPaymentSpent: 95f5b0266d8d8ec4455218bf218dc138778acda1352d8c22b49654b678195f04
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.