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.
c4cc88d13d39eb0625e63e6bf337ccf3329e5915113ef7f77c34661bdfd1a33d
Both payments are on their chains and locked to the same secret hash 5a1c69419347a477fa627514b6ea62d9a91ff04d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: c4cc88d13d39eb0625e63e6bf337ccf3329e5915113ef7f77c34661bdfd1a33d
- MakerPaymentSpent: 61195fa350dfc40a41e05a09cef8010bde727dd1e018d78ed0fd05a32f025b6b
79d8fa092129130d8895715635742594de8c9d5f5414bc0a9946b3944921175c
Both payments are on their chains and locked to the same secret hash 5a1c69419347a477fa627514b6ea62d9a91ff04d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 507bde2700a8178f678fc7ea800ff119f57eaeb3b2ca26b9b06be4238b02b5c8
- TakerPaymentSent · TakerPaymentReceived: 79d8fa092129130d8895715635742594de8c9d5f5414bc0a9946b3944921175c
- TakerPaymentSpent: 41c3a34d8e1b94d8d6c05dca86b5eea16bedb0935c55c195bbf17c2bfb2c8813
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.