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.
57b33ada9eccca8eb0fd43e9ca818562c32f9647a8d79ea8e2d1e0f020ae338a
Both payments are on their chains and locked to the same secret hash 776c807dcb8054a1d8e5895da4af164bceef5322, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 57b33ada9eccca8eb0fd43e9ca818562c32f9647a8d79ea8e2d1e0f020ae338a
- MakerPaymentSpent: 4edcab29ae2b8b6e2dbb4af16ee7b617a83e66f73f483535266556655acd968d
4d02a6e8ea42a4620fe8a0b0d9a76386d63cc2837ce93801557f58643c58cbd1
Both payments are on their chains and locked to the same secret hash 776c807dcb8054a1d8e5895da4af164bceef5322, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 05116de8e4cd3d874d1f3da8ec58762bda32f66f61f896408f8ab72cdfc5758f
- TakerPaymentSent · TakerPaymentReceived: 4d02a6e8ea42a4620fe8a0b0d9a76386d63cc2837ce93801557f58643c58cbd1
- TakerPaymentSpent: 3f9757ad56d2ad2b96b159881181ab1e467ee8c8d915aad3c710620e8bc18819
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.