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.
92c958c7da1f3110db3384425c581fe54b9b60cb636ea35e777cd19d15773d37
Both payments are on their chains and locked to the same secret hash 538c2e432d43866706e605140dcf7cda0e22d960, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 92c958c7da1f3110db3384425c581fe54b9b60cb636ea35e777cd19d15773d37
- MakerPaymentSpent: cab96575b680f23d26fcfa123c222db5f4f7f544e1caf2b17d0915ad6a0035e3
2b1b7eb44e388fb7d725c4fe1692962dbcf5ecb789260a25d24c33ada47e7207
Both payments are on their chains and locked to the same secret hash 538c2e432d43866706e605140dcf7cda0e22d960, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 059e9e5651da16db8bc5b42b1052458e92a626e16b90260b862453739d19aa82
- TakerPaymentSent · TakerPaymentReceived: 2b1b7eb44e388fb7d725c4fe1692962dbcf5ecb789260a25d24c33ada47e7207
- TakerPaymentSpent: 5431e066b94ef465176801abcf1ede0c9cb9a99a63260238ebb8763e64c2517e
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.