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.
bec7dbe293b6bd818f62377fef3929f62f44f3413275e40b464e1fdc751ca84f
Both payments are on their chains and locked to the same secret hash e00b6b62749983387454af2f076fe50a8a46cca2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: bec7dbe293b6bd818f62377fef3929f62f44f3413275e40b464e1fdc751ca84f
46eecae94ed5285cc9f4d555bf66e6efabeb794465ea744c2f0e810990b30a5d
Both payments are on their chains and locked to the same secret hash e00b6b62749983387454af2f076fe50a8a46cca2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: f99b65933b7eb7d1bb849ce93dcab4b0ff7766537eeb24f56cc004447b3944bf
- TakerPaymentReceived: 46eecae94ed5285cc9f4d555bf66e6efabeb794465ea744c2f0e810990b30a5d
- TakerPaymentSpent: 45f42fa594b127e2074fb8546c2979b8c959cb78f8fcc2b10bffabf81d0f9c1d
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.