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.
3913a919ba7934d85b231868f7fc811c31601a7cd524421b40ef0b164e0ccf69
Both payments are on their chains and locked to the same secret hash 1a9e36cb353a626998599a8008b9dd978bfc7119, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3913a919ba7934d85b231868f7fc811c31601a7cd524421b40ef0b164e0ccf69
- MakerPaymentSpent: 20d7b970abae0b9afd07d9f2bd6187bb5dca6bfd303e91669d4c367c27156e90
100c85a6639ac218fd5bdda4491a979fd7ca6f340233db8116628e255898e0d9
Both payments are on their chains and locked to the same secret hash 1a9e36cb353a626998599a8008b9dd978bfc7119, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a51973c787091d1a5581c7ee2e8e738560d8e34fb1e900de2aaa91c82c545f59
- TakerPaymentSent · TakerPaymentReceived: 100c85a6639ac218fd5bdda4491a979fd7ca6f340233db8116628e255898e0d9
- TakerPaymentSpent: ec46451ba50e52289fd86a4cec32c191f6964b1760f226b55f415ed974ed3793
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.