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.
672a18513716032fa7609763b8cdeb4eff68b636d6e0a473be22d74426790baf
Both payments are on their chains and locked to the same secret hash d22b494a81d393501264a39db9456f2e29930991, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 672a18513716032fa7609763b8cdeb4eff68b636d6e0a473be22d74426790baf
- MakerPaymentSpent: 4761a3879ff4111893213b5e6bc074f648bafe3265fde3a0c8b088bfe288e97e
8bd5a90b00b474334da1feab1310ba8fb653555d4b8d3f214466b64011922f88
Both payments are on their chains and locked to the same secret hash d22b494a81d393501264a39db9456f2e29930991, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 94b626644e463976e8f42b620f072ec529d9a551c0ccad1ed11d3dcfe058bce2
- TakerPaymentSent · TakerPaymentReceived: 8bd5a90b00b474334da1feab1310ba8fb653555d4b8d3f214466b64011922f88
- TakerPaymentSpent: 43538cfe35294d0c0c29af4bbc74542d3537e767b711e82e374c13e9c1a1af4c
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.