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.
6e8be107b2ef77fda3d325e4b6df9bd254f0efc6291fa4955b624f18c0d6a766
Both payments are on their chains and locked to the same secret hash 485744685c525d5e1d0757248a9c7b9e2ccafc4a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6e8be107b2ef77fda3d325e4b6df9bd254f0efc6291fa4955b624f18c0d6a766
- MakerPaymentSpent: ccc6cf5919ca37e68c6bfb8af808e207f4a107c7b32b8abbb5909673bee30bf7
45ed841b7013022bfa4e9fbf712a0aeeaefbd063d577fc4072d441e29a868685
Both payments are on their chains and locked to the same secret hash 485744685c525d5e1d0757248a9c7b9e2ccafc4a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 41e8564c17e094ac9160b1a01adde7195ea3a1912d09f298be3bb0f65b3499af
- TakerPaymentSent · TakerPaymentReceived: 45ed841b7013022bfa4e9fbf712a0aeeaefbd063d577fc4072d441e29a868685
- TakerPaymentSpent: 3a27fea2ff33c0c95d1d3b6f62d7828f172ee7b41a6283d6fe5da72d171fa12e
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.