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.
33cb3f7267fc0efdb3447243d972b1e9d18ec7152bc114a19d5e52e91dff48c5
Both payments are on their chains and locked to the same secret hash 0acdef2f57a3573c505e98bc0fae6ef3f8e5e9ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 33cb3f7267fc0efdb3447243d972b1e9d18ec7152bc114a19d5e52e91dff48c5
- MakerPaymentSpent: e5053cf06265d6afa39c29c08e2f576d10f33a686e316f3485a4f03a40fdd1d8
13f5eeea57e774d70751ce647463d8b887b85b37c8d9e68e663bca6e85911bdd
Both payments are on their chains and locked to the same secret hash 0acdef2f57a3573c505e98bc0fae6ef3f8e5e9ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8c6cfc6a4a12227f627c41df085adb531b30ef853c15c226cdbfab6d9d6408ff
- TakerPaymentSent · TakerPaymentReceived: 13f5eeea57e774d70751ce647463d8b887b85b37c8d9e68e663bca6e85911bdd
- TakerPaymentSpent: 3d4ed9144d9e653ca770960cc6fa58de1a78f8194a550e98e7ad1859f71524d0
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.