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.
63d72da2b8c84a7337d18ff27c1718dadeda7200ec206f5664589f619a9cdd4c
Both payments are on their chains and locked to the same secret hash 203bc4e4ea8671ef149c73d0f9c507ea5ce5854a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 63d72da2b8c84a7337d18ff27c1718dadeda7200ec206f5664589f619a9cdd4c
- MakerPaymentSpent: 37b5a6e0edeb5430a63c5cccf4016427aa87c97ed2abbe90bd53ed383aa77513
74863cedf99065f0734913bda77a22bb60c45af1dc26a9bc863d49f321c4bce1
Both payments are on their chains and locked to the same secret hash 203bc4e4ea8671ef149c73d0f9c507ea5ce5854a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6b29952522d6c4939de35ca70c8e9ae92032ad601427fbb132fca8df8ce42471
- TakerPaymentSent · TakerPaymentReceived: 74863cedf99065f0734913bda77a22bb60c45af1dc26a9bc863d49f321c4bce1
- TakerPaymentSpent: af4bea53b535fa6750f4ecc35d2c1fa8b9a14d9d9e307611041ae36f1ecccafc
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.