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.
a84d96d675826d71ab2b46a3624ddd413bcd7d002c2513740f664b27e3de5507
Both payments are on their chains and locked to the same secret hash 4dc189a794c50003db83351a98fa89016de46b9e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a84d96d675826d71ab2b46a3624ddd413bcd7d002c2513740f664b27e3de5507
- MakerPaymentSpent: 7e93cd868ccdf92812569762a64cd0e0fb5d984128c7ff551460f2a70c53af69
d3e364e8741f301ea517c3f2682e497b2f598465e66fc9d317fab68d806549f2
Both payments are on their chains and locked to the same secret hash 4dc189a794c50003db83351a98fa89016de46b9e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f9c2fd88d95b68363b3b6c08059e58672139e0b9c094549dcd6acd43154b77f0
- TakerPaymentSent · TakerPaymentReceived: d3e364e8741f301ea517c3f2682e497b2f598465e66fc9d317fab68d806549f2
- TakerPaymentSpent: 35ea5e5a859090eeeae851f34933ecb517e163cd81f442520fb9fe29dd337c93
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.