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.
06803e563ccb472eeb06efd9e9cdb693f2d9538744f6ead5d0d583d951098453
Both payments are on their chains and locked to the same secret hash d86816c0cdba26f7e44478eaf5e832be3f2380c9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 06803e563ccb472eeb06efd9e9cdb693f2d9538744f6ead5d0d583d951098453
- MakerPaymentSpent: 56d99580d59439fe9288a156732a38ae64f93a229d93ef8d1bbe4aab8989bad3
fb32b1e5c8b1552ce5e08087361fff5d1aaffeed7b82b6c7d6c91cb7100c4677
Both payments are on their chains and locked to the same secret hash d86816c0cdba26f7e44478eaf5e832be3f2380c9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2ac2f60817d0e07220ccae2a97ff3ae53685ebb6aa09583ee55f991809aad519
- TakerPaymentSent · TakerPaymentReceived: fb32b1e5c8b1552ce5e08087361fff5d1aaffeed7b82b6c7d6c91cb7100c4677
- TakerPaymentSpent: 102fc23b8c9928e6bffe6144d16bf2f307efe927c51d3d5b36ed031a96f7d320
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.