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.
63af162cf65fa28b6142f61b88f0ceab7b282277e522d4a4f6f39d4a506ec81e
Both payments are on their chains and locked to the same secret hash b07f982204fcf832343e84709bc7fa4ca8bd5650, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 63af162cf65fa28b6142f61b88f0ceab7b282277e522d4a4f6f39d4a506ec81e
- MakerPaymentSpent: 734c2459c33ec6103d0919dd723b2151426c8b36e72dbfe256edd20121214960
2c66979aa10348a8d16edc07cd26edd16112cfe6183fe174dbed0d351e63bec3
Both payments are on their chains and locked to the same secret hash b07f982204fcf832343e84709bc7fa4ca8bd5650, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d790036264e7de49e5170f857056deeae91e9554585b423d3e7f5645c051ef9e
- TakerPaymentSent · TakerPaymentReceived: 2c66979aa10348a8d16edc07cd26edd16112cfe6183fe174dbed0d351e63bec3
- TakerPaymentSpent: d5c6a0cbcd58d20bf8d160066c49f10c1e39ffd22e38a56b7eac0ad9c15eb731
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.