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.
5f4cff96d1f14e9996e4c98409f8bf634828475c5861a75a1ff37bce707f93c7
Both payments are on their chains and locked to the same secret hash b554209b9f27c63c236c2f62a5ae8e01b60e3653, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5f4cff96d1f14e9996e4c98409f8bf634828475c5861a75a1ff37bce707f93c7
- MakerPaymentSpent: b647dcb1f2ebf4c3306dfdcd289a8d0280235792074b8eb0d22ab451d8bc67e5
7bb39dcbbf256e1ebbdd13b09e73b4e39fd77bfb91976512ca8ae77abdb0cf68
Both payments are on their chains and locked to the same secret hash b554209b9f27c63c236c2f62a5ae8e01b60e3653, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9f7e47b0c628f5eb85271d7e81cea1203b52a0006efe82c486e862e3e3578a09
- TakerPaymentSent · TakerPaymentReceived: 7bb39dcbbf256e1ebbdd13b09e73b4e39fd77bfb91976512ca8ae77abdb0cf68
- TakerPaymentSpent: 2b1563068f48a7a77aa12362c429d97f6a51af10a385bce567d950269967e031
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.