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.
b2efa7c6fbfa6eb76cbae88d0156bea9ca930615b1e56a30d311163aaec49cf6
Both payments are on their chains and locked to the same secret hash 616e297cd67596fbd4dd694a78aefe12eeb868fe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b2efa7c6fbfa6eb76cbae88d0156bea9ca930615b1e56a30d311163aaec49cf6
- MakerPaymentSpent: 324da5f6f67af929ab1b344d86ec7fd4ce63975eaeeb0c1fcad8037657a6190c
a3a6c3685246f358d77521bb3e97ceebc5cd203b05c764210dda91978f400a91
Both payments are on their chains and locked to the same secret hash 616e297cd67596fbd4dd694a78aefe12eeb868fe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e1473536d7c8288d7bdc0941e896acda2415d4a4b8992499af3cab1188b81151
- TakerPaymentSent · TakerPaymentReceived: a3a6c3685246f358d77521bb3e97ceebc5cd203b05c764210dda91978f400a91
- TakerPaymentSpent: f52b909b55aae438e2952426e304ba678a0cb68fe1435c8a64808373b6bd629f
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.