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.
6a67f7b4263964219ed5423e71d268c6852017f3a828c2b2b372a3c65e6104fa
Both payments are on their chains and locked to the same secret hash 99c9c5fd7052a03d354997f0bd7b27fca2536673, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6a67f7b4263964219ed5423e71d268c6852017f3a828c2b2b372a3c65e6104fa
- MakerPaymentSpent: 0f8eb6f632cbcfe9c3429ecc44697258141f36012a1d796f87fbe88c1aeadca6
ac071828cc7579ba86b4ee659c0dec49f9053241693b8198da80cb6270556683
Both payments are on their chains and locked to the same secret hash 99c9c5fd7052a03d354997f0bd7b27fca2536673, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: faef427b0057719a75c6eec16905b50ae089b03d3f12ded9da152c9838887b32
- TakerPaymentSent · TakerPaymentReceived: ac071828cc7579ba86b4ee659c0dec49f9053241693b8198da80cb6270556683
- TakerPaymentSpent: 8ddea117631493746192cb36a03db2d65b7366e1787ac348cd1ea72e5e1ae119
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.