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.
621d66fe86c6fa2cab203010e57e787ce427fd7b912fa8fe97d231c33db8f15c
Both payments are on their chains and locked to the same secret hash 07d43a827dd20bf1c860accba2c9786e9737e832, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 621d66fe86c6fa2cab203010e57e787ce427fd7b912fa8fe97d231c33db8f15c
- MakerPaymentSpent: 524d5fe3d4aaf2249296f2fd7180d1dd96b34dd6a3e25bc8d189ce4abed565a8
9d556d81aa2b0200b26e54b4793d1eed0cd8ae145ccef7e4f0df12c7ffea36e7
Both payments are on their chains and locked to the same secret hash 07d43a827dd20bf1c860accba2c9786e9737e832, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 624095cd4b6bccd6cb96479d9cf3926d5ace3b898d52a18bdb3d7f91b457106e
- TakerPaymentSent · TakerPaymentReceived: 9d556d81aa2b0200b26e54b4793d1eed0cd8ae145ccef7e4f0df12c7ffea36e7
- TakerPaymentSpent: 5b34e4c04e6c5495c4ded3f029c2988dbd606ff5fb5b5d08c1c41bfb17560d77
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.