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.
0c3aeecbf0c923327a3cce35ecbbe2bedefb98f04b094543263d539ed1985b4a
Both payments are on their chains and locked to the same secret hash b4adacc6218d86557b523e2f0097346c853fc396, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0c3aeecbf0c923327a3cce35ecbbe2bedefb98f04b094543263d539ed1985b4a
- MakerPaymentSpent: 63d0f3d49832a6bf5caf5cda21b5e7ce51e22bd7c18c2ef573f73f7c613dfa14
1b4e7f57abc79d64f76a02986b65116ecb1dabcb2914a4c4a271cfb14ee6023e
Both payments are on their chains and locked to the same secret hash b4adacc6218d86557b523e2f0097346c853fc396, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 67b3c8bd9bac9b707713d481fe4a62051ddb733acc9babc25621163386477ca1
- TakerPaymentSent · TakerPaymentReceived: 1b4e7f57abc79d64f76a02986b65116ecb1dabcb2914a4c4a271cfb14ee6023e
- TakerPaymentSpent: 35253c00135b3e424a0f024a181137ace50d8fa0caf3cfa56792588f09a86e4b
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.