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.
dd18afa2ec823b5d3079c183159fb6176d6989fc333b60cb2010a728bd28a699
Both payments are on their chains and locked to the same secret hash 6b73c161d16f9e48db987e7bb928bfded01ad072, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dd18afa2ec823b5d3079c183159fb6176d6989fc333b60cb2010a728bd28a699
- MakerPaymentSpent: 152c089cb5e408195f526143b65622c0e79ad5c2ddc98518c0b49459a9125d8b
d522efa9ec8fb7ece842fc15b5c65466ead00aed231e056623c1756b83001083
Both payments are on their chains and locked to the same secret hash 6b73c161d16f9e48db987e7bb928bfded01ad072, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5ebf0a46041e630ac8c4a29d1496ab2f6bd372a8a952bc19ff1424bf3c597161
- TakerPaymentSent · TakerPaymentReceived: d522efa9ec8fb7ece842fc15b5c65466ead00aed231e056623c1756b83001083
- TakerPaymentSpent: 1745d518e209ec092e935ee8f4bfeb8ae4cfffff1de9d1afaf5534266c598afe
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.