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.
d5f3eefb827f94c18cdc1cdb048f8a4b2159acfe4af2e86a714bec0c8fa4e43e
Both payments are on their chains and locked to the same secret hash 3f85ded781caf6f9a2b6fd3ec6f28c23bbe7a060, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d5f3eefb827f94c18cdc1cdb048f8a4b2159acfe4af2e86a714bec0c8fa4e43e
- MakerPaymentSpent: 5193e73af6941ddb0c855ec07851eb3c218bfdd71a571865ad210f1da4e397aa
45c4fe69f2a3a1b63b56bf1a81e08d8427191b3347d0520e79121b49a74dcbb0
Both payments are on their chains and locked to the same secret hash 3f85ded781caf6f9a2b6fd3ec6f28c23bbe7a060, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7a17a981309852fbd0c1f44c0965be91fc67bb50a2a64a2569cc7430c19673e6
- TakerPaymentSent · TakerPaymentReceived: 45c4fe69f2a3a1b63b56bf1a81e08d8427191b3347d0520e79121b49a74dcbb0
- TakerPaymentSpent: 77e4f9d9d84587515ffeb5c1bbbe539e9afc0f36b3f136de7c2aedf7d817740f
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.