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.
0f16904b448b5d951bc34f4891dbe3f744d3c25dbfbd73aeb88e8c4649dcc6e0
Both payments are on their chains and locked to the same secret hash 79d7eb15e034729fe7ed60083fe114441747ee01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0f16904b448b5d951bc34f4891dbe3f744d3c25dbfbd73aeb88e8c4649dcc6e0
- MakerPaymentSpent: 6f4605229d677bfb7c1dc00c0bfc340751dea9af364614f4d4cd60f9061281ac
d73fade9a8aad73b451453e24bc263be340fafd863223a3f3e0120707edddea3
Both payments are on their chains and locked to the same secret hash 79d7eb15e034729fe7ed60083fe114441747ee01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 14a8d317d133125c3a10095fdd00afafa3cdcc3d1150e6a1c77cb5f101e3e44d
- TakerPaymentReceived · TakerPaymentSent: d73fade9a8aad73b451453e24bc263be340fafd863223a3f3e0120707edddea3
- TakerPaymentSpent: 2fc338d94a85bae55a3a6a73737ad7fdbc90dd6134434b995ff74e8d84448510
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.