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.
3e974dceba70a8aab61df8642ecab137ee527aaaa505938994d5b39333053a94
Both payments are on their chains and locked to the same secret hash d3a89cf64438dbe0abae5f59640f2d86d9a0bdcc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3e974dceba70a8aab61df8642ecab137ee527aaaa505938994d5b39333053a94
- MakerPaymentSpent: 64a95458e15fac95fc9bdd05221c7ad612c8d012ecdd4d63cf9e82725c557546
518ae3122190e12917d7fe0753afb9a918261949f6c5b7bbf51368ed9ca3ee42
Both payments are on their chains and locked to the same secret hash d3a89cf64438dbe0abae5f59640f2d86d9a0bdcc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fe0dc71a040765addfb460dc97f4e4099c337f3fb6a90dcd0e6894180b560ebf
- TakerPaymentSent · TakerPaymentReceived: 518ae3122190e12917d7fe0753afb9a918261949f6c5b7bbf51368ed9ca3ee42
- TakerPaymentSpent: 0a86fa118b4b6b94c6163cb3f241147109a9fa06ef24d6c1ef9f951f3fc73a1e
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.