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.
e03fba9e4a9df460d5751cd1409f772dcc3b1e30929ec313ec8e7f172660349d
Both payments are on their chains and locked to the same secret hash b777befaf9ecac8a80bebb0bc09fd50b8554d1d7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e03fba9e4a9df460d5751cd1409f772dcc3b1e30929ec313ec8e7f172660349d
- MakerPaymentSpent: 2747b29a181e6a00f927cd2c3274a4a801a5a8b6a94d5c54b84c79d6b62bcdce
a98e74452c861bd95f53132e16e223270c9a708e89dbf016b6d302d491ec6c82
Both payments are on their chains and locked to the same secret hash b777befaf9ecac8a80bebb0bc09fd50b8554d1d7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 45963308ec3b653fc24208a19790328b43ac3f6b46967772a793999f762d5276
- TakerPaymentSent · TakerPaymentReceived: a98e74452c861bd95f53132e16e223270c9a708e89dbf016b6d302d491ec6c82
- TakerPaymentSpent: c9620a81489f2c53f4fe686554d02adb4d1b051cc9aa5d4b8a1433a5224e8db3
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.