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.
764758316e2548db969caa9c6e73c059b70b0a31f46a5537c564bddcaf86fe12
Both payments are on their chains and locked to the same secret hash 190fea088f2f87a43e358b17dc12fcde0a9f1b93, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 764758316e2548db969caa9c6e73c059b70b0a31f46a5537c564bddcaf86fe12
- MakerPaymentSpent: d006e289891126d355b0382b2e796483dd5861ee0292e63edda3980808fcd505
b7b2aeef03480fa5a341cc848480720fc6f404dc0bdded07ee13f22321d71296
Both payments are on their chains and locked to the same secret hash 190fea088f2f87a43e358b17dc12fcde0a9f1b93, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8905059d34f9899d01c378870952b28eaae25e1f4bfa04e4f643e2f227e27f1b
- TakerPaymentSent · TakerPaymentReceived: b7b2aeef03480fa5a341cc848480720fc6f404dc0bdded07ee13f22321d71296
- TakerPaymentSpent: 579462af62ac007ea5432a00ca0240dc9de1adb741bb14f89702624b59843be4
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.