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.
01eaf0ecb056d31c29613b82ed021b92e2921846ae5785fba258e289ca5e1782
Both payments are on their chains and locked to the same secret hash 4ce53d10a9d8daeacb65597d6a2e1386febeb9d3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 01eaf0ecb056d31c29613b82ed021b92e2921846ae5785fba258e289ca5e1782
- MakerPaymentSpent: 91f2e283e7ab338685c86dde772f3f7c78d8da8ffc1d1c090363a445f2d1c500
37caba929f236af9f3ce0db7879c491f3afdd326db53060fb0660dafba19f882
Both payments are on their chains and locked to the same secret hash 4ce53d10a9d8daeacb65597d6a2e1386febeb9d3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2d654cb3d72eb277372c22ff268d0e01ab5a47b86fb8ce2338208f9c3ef6d506
- TakerPaymentSent · TakerPaymentReceived: 37caba929f236af9f3ce0db7879c491f3afdd326db53060fb0660dafba19f882
- TakerPaymentSpent: ee723d891d6b5623c1aeda340ec4ec57ae9e9a55e8f948759bdb6b1ebfc3a578
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.