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.
9b842ec06290b9c2ed19a22655f09b95eef6d5c4ca6caa697469af568937d65e
Both payments are on their chains and locked to the same secret hash b392eb22d10cb57d513c9e74204db8e26e934975, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 9b842ec06290b9c2ed19a22655f09b95eef6d5c4ca6caa697469af568937d65e
- MakerPaymentSpent: f5f5e07b6a9e92caf93ce1e4bf610656e33fd5c78df775566c4dae32b86b6f6e
6de9e44e4840de40774caf0441073571835842874592bddf193aa320d287d8b1
Both payments are on their chains and locked to the same secret hash b392eb22d10cb57d513c9e74204db8e26e934975, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b41bcbb64094d6509a1419871ef9c26783757a0c7cbc476674ebf412589fc578
- TakerPaymentSent · TakerPaymentReceived: 6de9e44e4840de40774caf0441073571835842874592bddf193aa320d287d8b1
- TakerPaymentSpent: b288d1baaa08e480d554ec79e25a776cbfaa949d4d501d060e643dbe8d293ebb
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.