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.
fa3c62612af3562a53928dfba45c57b5a9edde7d355c3cf6c4cd8446b6f5a27b
Both payments are on their chains and locked to the same secret hash 68d24c2f0d6bef664344e24c87924bde1f675386, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fa3c62612af3562a53928dfba45c57b5a9edde7d355c3cf6c4cd8446b6f5a27b
- MakerPaymentSpent: e3f8e8090efe3f4669ae093ff19e2daf74d1c7684c1d11a98cc606f5b5363f98
e8ee1817694cdc5c01633e8da288d6a52ca22b0e3409870c58ae2dfbe66860c0
Both payments are on their chains and locked to the same secret hash 68d24c2f0d6bef664344e24c87924bde1f675386, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3bb6360f88791ef3a6b3c18957e8bd2533122f8f70f37a1cddaa0d7de77b5b95
- TakerPaymentSent · TakerPaymentReceived: e8ee1817694cdc5c01633e8da288d6a52ca22b0e3409870c58ae2dfbe66860c0
- TakerPaymentSpent: d3994e832f2e5c093211b21134a5b0a179a790fd561d88ed6a533c7745e75d1d
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.