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.
3ee8e4049924f4a8c1182ec1e3d7bbdfa637b9ac0af974a0f6e110753cceebba
Both payments are on their chains and locked to the same secret hash 2320cc08e765d5a9ae8a18e15c640e523bbd58d6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3ee8e4049924f4a8c1182ec1e3d7bbdfa637b9ac0af974a0f6e110753cceebba
- MakerPaymentSpent: 05fec9c8993dd6c6e1c7f9710ee2402b823cb9e2253c41057dedfdaf31170c01
db050360a45ed1a8055048d2d5b5c8e8cfb95dc39691932a2141e170218a46c5
Both payments are on their chains and locked to the same secret hash 2320cc08e765d5a9ae8a18e15c640e523bbd58d6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1ad566bcada54870a6949fe5a634c7ec06812f7386c47bd5a2fa25da840acd6a
- TakerPaymentSent · TakerPaymentReceived: db050360a45ed1a8055048d2d5b5c8e8cfb95dc39691932a2141e170218a46c5
- TakerPaymentSpent: abf0b8338f968df4d8daeb5ab307b17817dc4c12f529f145640c2e5ed0c7639b
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.