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.
64dd31e16e18402b069d9fa5767416d3a5e727b7b65ab440a2a26c4341558c45
Both payments are on their chains and locked to the same secret hash 5f57f39803cf974c8dc34581e1d00f2240803722, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 64dd31e16e18402b069d9fa5767416d3a5e727b7b65ab440a2a26c4341558c45
- MakerPaymentSpent: 5dde4e37e1285c188aab226be11cf1728bfe5b2f76865b563aff98c651d71510
6faa1025dfa45c688314fc16813166c421ad0b749f34510920a3e4132ccf4b72
Both payments are on their chains and locked to the same secret hash 5f57f39803cf974c8dc34581e1d00f2240803722, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8ae97ae929777016ab0184e8ad157ab314cd6d877f30a29157a65871a4980be6
- TakerPaymentReceived · TakerPaymentSent: 6faa1025dfa45c688314fc16813166c421ad0b749f34510920a3e4132ccf4b72
- TakerPaymentSpent: d2de05933be7674cba1af5b622858ae0dd7be1fee8b55dff2d506f4437e357ff
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.