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.
9100dc3eade933f7fd1cdf129882d4c1c68f6a82fbfc35ac3f2e98e52c0de049
Both payments are on their chains and locked to the same secret hash bdfd6e999e8b15ad963fbcfb6a78557f83c0e862, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9100dc3eade933f7fd1cdf129882d4c1c68f6a82fbfc35ac3f2e98e52c0de049
- MakerPaymentSpent: 7e8f27701863af80ebb3bbc3ee165a148d28def3057271545ca137f51e3931f7
e525c37911360424052f415e0d57fa4bc3b8fd61e57e262c35bd3b49d938f538
Both payments are on their chains and locked to the same secret hash bdfd6e999e8b15ad963fbcfb6a78557f83c0e862, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f98d135e18d2d6beb3975637e2fe5eb810d84bdce19200742bc64609a5f917b8
- TakerPaymentSent · TakerPaymentReceived: e525c37911360424052f415e0d57fa4bc3b8fd61e57e262c35bd3b49d938f538
- TakerPaymentSpent: adbcda0a29b14fd10bb26bc4a14b5c8e32e919a98ef05ebc72ce386a83bbc065
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.