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.
d7d2ad3ab31aad7691b3c3f4fb61082e3b07a9dfa09cf8deb7d9f345cd746159
Both payments are on their chains and locked to the same secret hash 47da135bc03d0484887f89b7f6d4e76b12ca1691, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d7d2ad3ab31aad7691b3c3f4fb61082e3b07a9dfa09cf8deb7d9f345cd746159
- MakerPaymentSpent: 89e5cf14ab2fc04392249ec2745d50459313df5d7f0637abbaeeb0c226ac6962
3912368579538b13e3000ec53f7ea684db3e4622e22d318579ec491e5e4f871b
Both payments are on their chains and locked to the same secret hash 47da135bc03d0484887f89b7f6d4e76b12ca1691, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5fbd4fb20174911b3cc23583117c6b5ad982888a44f3d31e1d8e1057966ac218
- TakerPaymentSent · TakerPaymentReceived: 3912368579538b13e3000ec53f7ea684db3e4622e22d318579ec491e5e4f871b
- TakerPaymentSpent: da8f87661bcf142244288287c5f5952ba5dfc1e22e7e4b63ed57cc4ed50f80c9
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.