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.
3aee335c40c544c268c6d1bd7859c3f9377128c2e946051d8e13df245ec85544
Both payments are on their chains and locked to the same secret hash e71c88084fb162421dbf390e92101319942ce1e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3aee335c40c544c268c6d1bd7859c3f9377128c2e946051d8e13df245ec85544
- MakerPaymentSpent: 04176c129b3bb848574d7ad6b8633065fe044f89bcdeed7260690be083eb3035
8d16208c10972a79c77ac5e1141156922e6bf27d3017ae14d66c5ea2799f862e
Both payments are on their chains and locked to the same secret hash e71c88084fb162421dbf390e92101319942ce1e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 830f69c59dc1a416af510a23af9fcb9095780d8b54fc71b64c8eb56647d43923
- TakerPaymentSent · TakerPaymentReceived: 8d16208c10972a79c77ac5e1141156922e6bf27d3017ae14d66c5ea2799f862e
- TakerPaymentSpent: 3ac8bc416294c20b0363da72b62e3d5ed6bc90ad10090220fdfb4ecf2c2e1575
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.