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.
d38da65a50035e407e7a0e0f73c534b44696af043c03d7286605bb0dd611eeed
Both payments are on their chains and locked to the same secret hash ddbb00becb179226fc16be7f5625112a6b924adc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d38da65a50035e407e7a0e0f73c534b44696af043c03d7286605bb0dd611eeed
- MakerPaymentSpent: 3b59f58c788de2e8d4d496864d800b03ce45af24920795ab1113c361b5997931
f543aca51036009de17da1e633b4a511c55e77163ef4d62613564ba6aad9a9a4
Both payments are on their chains and locked to the same secret hash ddbb00becb179226fc16be7f5625112a6b924adc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2605870424fe7a66b0fd3ae8c93b6dc2cb2901edf2e65acfc581670cc2f6a063
- TakerPaymentSent · TakerPaymentReceived: f543aca51036009de17da1e633b4a511c55e77163ef4d62613564ba6aad9a9a4
- TakerPaymentSpent: d149f6305bb54e8d68563442fb36915d89d7ccbc9b2d5a8fffea79de13ee8639
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.