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.
89a8caab0898ba57cafe6a5c891e00f7eff2961e8c54e8f7bafe7f1c3fb652ea
Both payments are on their chains and locked to the same secret hash 96987aa9b1fbcddacd3186363f37b1492e73ea18, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 89a8caab0898ba57cafe6a5c891e00f7eff2961e8c54e8f7bafe7f1c3fb652ea
- MakerPaymentSpent: c8e7b9d3679959bf8e2bce3a0d01c745b37fa3c789082fb5a0c311deb3ef11a9
dfbdba966d99cea777877c7c55ba93f4c0b32a3907d1c88f45a71f02455fc3fb
Both payments are on their chains and locked to the same secret hash 96987aa9b1fbcddacd3186363f37b1492e73ea18, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3be4efbce34fc1d5c37cf8aa0364a582d8bf5f6be484473b060f56a1db9d2d02
- TakerPaymentSent · TakerPaymentReceived: dfbdba966d99cea777877c7c55ba93f4c0b32a3907d1c88f45a71f02455fc3fb
- TakerPaymentSpent: 6d00773fd69ea7fa3b8488cdc4007492417e6ba1831beb6816b84964ab45fa7e
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.