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.
bd0ac1a3423dcb2cfe76997a592675e54861d5dc328fd0491281b24bf87c8c54
Both payments are on their chains and locked to the same secret hash a8d80a79d30b55ae1572ebfe015371bbc2aa8f76, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bd0ac1a3423dcb2cfe76997a592675e54861d5dc328fd0491281b24bf87c8c54
- MakerPaymentSpent: a9a560da106f637c5de804069da19115af08aeaecd09824d33534fe14e5ceb01
1558531038602899935832adaf4d35012cdad17592467e1f673ea689e12d51e7
Both payments are on their chains and locked to the same secret hash a8d80a79d30b55ae1572ebfe015371bbc2aa8f76, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f885323bf6526eda7d04e444646695ad7e49f5767bf3281c0818197f7c743aec
- TakerPaymentSent · TakerPaymentReceived: 1558531038602899935832adaf4d35012cdad17592467e1f673ea689e12d51e7
- TakerPaymentSpent: f3511450daeac187f5c7af0925be577dc8c4a25d87670fc9136e90a148e9dc45
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.