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.
f8394901a28635ff0c9214b20c9f27ccbdd6bc99e8b6dd41fa2f3cf9be242420
Both payments are on their chains and locked to the same secret hash 5de5126fdd225b373a0d1f08fdbc2d4ef184b4d8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f8394901a28635ff0c9214b20c9f27ccbdd6bc99e8b6dd41fa2f3cf9be242420
- MakerPaymentSpent: 4c657c0ea8926c375127f189e4e406538d5420c111328f69c13b762650a66b42
8b46034ae36132f55d32c470d9d1556f57d4d21c40a472ec11e0d8439f7a096b
Both payments are on their chains and locked to the same secret hash 5de5126fdd225b373a0d1f08fdbc2d4ef184b4d8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2dd767bdf84a25867ae167d5d25d4fd6877b9e4f455c9b803c56e3aabd219d8f
- TakerPaymentSent · TakerPaymentReceived: 8b46034ae36132f55d32c470d9d1556f57d4d21c40a472ec11e0d8439f7a096b
- TakerPaymentSpent: 5b0d9ac3c20db816e1b6cadf94349b94fce05b636960db4c26966337fc5c699d
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.