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.
1e9fd47eae525494e891fc0cc2c1c7520367c91f3cb11ba1b1b24e95a170ca27
Both payments are on their chains and locked to the same secret hash 6d4ff59b7c1e3a895bff07adbb14b6f74fcaa7dd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1e9fd47eae525494e891fc0cc2c1c7520367c91f3cb11ba1b1b24e95a170ca27
- MakerPaymentSpent: 9ae4312ea569c1dfe2051d245ad5065f6fca5caa0ec101687d0fa7dc00d75a94
64b1b3606fe1a4f975036792342efdb5a13ab0a79be45180f5d44f54c65a060c
Both payments are on their chains and locked to the same secret hash 6d4ff59b7c1e3a895bff07adbb14b6f74fcaa7dd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 61ceb16c9d902caedafccc902d153c0e264fdf36a2c99eadc60bf674349b383f
- TakerPaymentSent · TakerPaymentReceived: 64b1b3606fe1a4f975036792342efdb5a13ab0a79be45180f5d44f54c65a060c
- TakerPaymentSpent: 93cff2fe89a53b5d8e31c9d982911ae283e75089d03d522541831e4310fef411
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.