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.
b974af7a3677680ea32544f75fc38c573f877f6d922850ea4ab9ea287c53d55b
Both payments are on their chains and locked to the same secret hash eacea04284a0b54627ff6747c49b76d2c959e4c4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: b974af7a3677680ea32544f75fc38c573f877f6d922850ea4ab9ea287c53d55b
854427983d7a878fc74bd4543c91bdadb0f7c8fa6522010fe342e6aa1d7e99c6
Both payments are on their chains and locked to the same secret hash eacea04284a0b54627ff6747c49b76d2c959e4c4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 769e529fbce023a0bd6d468bcba6ae8230a7aabce9fd4b5cb91d1f44e1dc0eaa
- TakerPaymentReceived: 854427983d7a878fc74bd4543c91bdadb0f7c8fa6522010fe342e6aa1d7e99c6
- TakerPaymentSpent: 357b9f3f946df058af957a7e52cd33b011ab2f9f50a94c2dcc71a08290b5f41e
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.