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.
8e3a9af139fb1e8ce0cdad5844fd3661f16398a091e68fca5468729b25e1e965
Both payments are on their chains and locked to the same secret hash 589666f5a808b7fefde71a306c826743af43580d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8e3a9af139fb1e8ce0cdad5844fd3661f16398a091e68fca5468729b25e1e965
- MakerPaymentSpent: 676747534c0ec5c856b20fe372a18b4aba9215ecd220b00d99f290dfb89d418b
6e39f63826f2a4b37704739f0c062a55dcb9c0fbbf0d2caf629db3f0558681a9
Both payments are on their chains and locked to the same secret hash 589666f5a808b7fefde71a306c826743af43580d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9aed868ead5618700e8985ac05a737e4d6d6d2c873713ae92d97cdcace631245
- TakerPaymentSent · TakerPaymentReceived: 6e39f63826f2a4b37704739f0c062a55dcb9c0fbbf0d2caf629db3f0558681a9
- TakerPaymentSpent: d4038febffc851528816d6395d7a177aa2add6e7a923096fddaf5fda3c4868a6
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.