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.
2dec04e96485bcaca2bd85ab05ec804f77afdc2a8d47cf9bbcdaea803748bb74
Both payments are on their chains and locked to the same secret hash 983d9d9b83f9a312be4e27b87e1446a10d236ece, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2dec04e96485bcaca2bd85ab05ec804f77afdc2a8d47cf9bbcdaea803748bb74
- MakerPaymentSpent: 35835d91d9554287c529f51a0a84a4efd3567af6e3ff95e7911ed4202d859482
78ed487af8ea21480b6e448a4580c54b91902c8cb97c1dd38009ada32601a860
Both payments are on their chains and locked to the same secret hash 983d9d9b83f9a312be4e27b87e1446a10d236ece, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cd5e9b457a20e01ca7eacb0c5d4b64746f6bdd0653c9891237238ea39b768d67
- TakerPaymentSent · TakerPaymentReceived: 78ed487af8ea21480b6e448a4580c54b91902c8cb97c1dd38009ada32601a860
- TakerPaymentSpent: 581366c3e21a95905060a4ac140aee89697069f7f0acbab60463387b429b3717
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.