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.
0a3c65ef86c456cf9187664c3b21b977f5fd4561b379c226b10c4418c21b4408
Both payments are on their chains and locked to the same secret hash ce486dc02c288ba287d9b0e1fa2eb1bdb1b13939, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0a3c65ef86c456cf9187664c3b21b977f5fd4561b379c226b10c4418c21b4408
- MakerPaymentSpent: 28319d1dade39cb4cc7843479531e0a15f1a776845a0c0ab14db48699c21bd01
9d9f2a61c8d566b86750c9a80b7dc59ce9c7f5620689963c6df71ea039ac3fa2
Both payments are on their chains and locked to the same secret hash ce486dc02c288ba287d9b0e1fa2eb1bdb1b13939, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 40261e6be5e6c035fee488117cc640585d74617d6142fba1a04b46185b9630fe
- TakerPaymentSent · TakerPaymentReceived: 9d9f2a61c8d566b86750c9a80b7dc59ce9c7f5620689963c6df71ea039ac3fa2
- TakerPaymentSpent: 6011c483405e50670078a169e39ef8d88abf55f0fc72e0b4b504c90c921b372c
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.