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.
d2f64c1a689949f26a478a73495381e087616d86c1424b3f3b71ac4bf4ad5a93
Both payments are on their chains and locked to the same secret hash e1753792a2a00a56e9a2bc63aadf683bcea2193c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d2f64c1a689949f26a478a73495381e087616d86c1424b3f3b71ac4bf4ad5a93
- MakerPaymentSpent: 6ce472f64c28c77a5b66de999f9b78423a9909343dd97aca157f90aff5963036
c56799a8e24d3195b6c796cc36f05d81a6e88df94b689ede490d33dab7548b46
Both payments are on their chains and locked to the same secret hash e1753792a2a00a56e9a2bc63aadf683bcea2193c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ded6b475f338bbe4fe47db6ae0f01844d220baad6a3433b2dfff2b387a3d6bd1
- TakerPaymentSent · TakerPaymentReceived: c56799a8e24d3195b6c796cc36f05d81a6e88df94b689ede490d33dab7548b46
- TakerPaymentSpent: e51f3b7b9182ef7cd8e8a0aab0ae88eeae932a450603c2fc1044f900393098bc
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.