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.
62749d06f721b301bd362741d3014992bb28e1eed468ec2a6a1b4beeb546249e
Both payments are on their chains and locked to the same secret hash cdcb1ff399ffba17ef6a03c30565f8430bf400e3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 62749d06f721b301bd362741d3014992bb28e1eed468ec2a6a1b4beeb546249e
- MakerPaymentSpent: c53b5c3b937c6128f8219b4d36c6afa78b20147e52fb9d05f08a4780e62d0ef0
7c630471557eec8cbf565fe298f943d898c1e3b339f181bccade785a1946cea6
Both payments are on their chains and locked to the same secret hash cdcb1ff399ffba17ef6a03c30565f8430bf400e3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 710b163d5b013e3218a6537290e8f1a8f1b07f5c5d6641005882984c976a57c7
- TakerPaymentSent · TakerPaymentReceived: 7c630471557eec8cbf565fe298f943d898c1e3b339f181bccade785a1946cea6
- TakerPaymentSpent: ac0b8c37ca1ead3905cc20f3dfa4cab21236f346108172cbd1a31ea093391ec8
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.