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.
3b466ffff00a003a5b7745f87c5a58d7aff9636577b81501a2b1d802f227f10b
Both payments are on their chains and locked to the same secret hash 3e726e9e62a6a6dee7b0af5ab2e6e1c7937ea2bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3b466ffff00a003a5b7745f87c5a58d7aff9636577b81501a2b1d802f227f10b
- MakerPaymentSpent: 0f3d6895907e4941f28e8c5a43a323730c83eb30510fae55fa122475c19a59cd
dee16ea122f060807707295e1e4c95281421debc27ac0fc65671179cf5f619b1
Both payments are on their chains and locked to the same secret hash 3e726e9e62a6a6dee7b0af5ab2e6e1c7937ea2bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fef922ad9d298b9744cf54e8d1e29d4416b50018fb750ba02a81ca1a7d5896f4
- TakerPaymentSent · TakerPaymentReceived: dee16ea122f060807707295e1e4c95281421debc27ac0fc65671179cf5f619b1
- TakerPaymentSpent: 6413963a77fc9cc116c1c750b2e0c0cc639d7f5a2fa42fb7a3da9d4e9392f234
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.