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.
82bd4dcffe6bea565ad20fce594d3cecfd5efef538fce4513a165477cae9454f
Both payments are on their chains and locked to the same secret hash 18046a647fd43dc0b1ab12f799e34855d93a39a2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 82bd4dcffe6bea565ad20fce594d3cecfd5efef538fce4513a165477cae9454f
- MakerPaymentSpent: 89857b41ccb2261ceedc4d9e877fa9a283f8cbd81d917f1302ac3b6db3502e87
441d999c5c339c038a1267e99749f657bfd09c8998c728079f8191a4a2804fa1
Both payments are on their chains and locked to the same secret hash 18046a647fd43dc0b1ab12f799e34855d93a39a2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b6ec40eb2eb478f93a3b8399a7a70e05ff2771eca9fcf8f619851bd679d132d1
- TakerPaymentSent · TakerPaymentReceived: 441d999c5c339c038a1267e99749f657bfd09c8998c728079f8191a4a2804fa1
- TakerPaymentSpent: 933db68ca39224353246d4faea06098991aa35cc0c9b66dea8b6eea32a2d2037
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.