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.
bd570b05278b555742db5ee564950b600c0e429f275544cb3d7b7082b9554cb4
Both payments are on their chains and locked to the same secret hash c6f1b0202f366446ec35ec6576cee2d71b0239b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bd570b05278b555742db5ee564950b600c0e429f275544cb3d7b7082b9554cb4
- MakerPaymentSpent: 0666c6a3435ed8feb152e4fb8a4d0772f7318e9c88a0596fadcca67dbc78ca41
58976ed6b027fada18760b0f762c2ca159160d5d6cb8f74fa1d83db88518feaf
Both payments are on their chains and locked to the same secret hash c6f1b0202f366446ec35ec6576cee2d71b0239b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9e003fca43c0ca6bb35cbb6a91b1c76059dadcd384cd24b90e9aa36913f84d96
- TakerPaymentReceived · TakerPaymentSent: 58976ed6b027fada18760b0f762c2ca159160d5d6cb8f74fa1d83db88518feaf
- TakerPaymentSpent: aee82e4113e454172b53d8f687db28dacf2ea4571b3d6959aa0d7533985251ae
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.