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.
7c726f2de213a2414db718e37e33991f3484b620ab750cccd2b3744aebfacb0a
Both payments are on their chains and locked to the same secret hash 13916449a1a3bc1b3b2df377f47b4dc1c3dff09e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7c726f2de213a2414db718e37e33991f3484b620ab750cccd2b3744aebfacb0a
- MakerPaymentSpent: 000f509c5b8e5675bc882b2922e4e742f02c1e84265084ce32b5f506f9db4c1b
50fbc29aa31d28a8352536200de3f2fc1425a3966665c857b0064e07f4df430f
Both payments are on their chains and locked to the same secret hash 13916449a1a3bc1b3b2df377f47b4dc1c3dff09e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f45b8b03cc87c486fd089e4d0df3331754a8f2b7f36d7d1099333edbc082dc20
- TakerPaymentSent · TakerPaymentReceived: 50fbc29aa31d28a8352536200de3f2fc1425a3966665c857b0064e07f4df430f
- TakerPaymentSpent: cc0e5ef583a77cde125971ae64ddfbb57082ae4dcc9bd73f380c9f506ad79b8f
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.