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.
6dd417b97da070db0ded18963422b0e5a1f6443ca64b4b16a24acfaa93fbf507
Both payments are on their chains and locked to the same secret hash 54ac399d437e752053e258cf53fde56ce3fb1609, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6dd417b97da070db0ded18963422b0e5a1f6443ca64b4b16a24acfaa93fbf507
- MakerPaymentSpent: 08c241cae5341d35a66ba4ef88a29ed55b6b6d3f1856544571583fa264ca7199
4bf7d575ead8ba0b67e8c7ba2b624f408cf7a5e3549108c7e231408d94979022
Both payments are on their chains and locked to the same secret hash 54ac399d437e752053e258cf53fde56ce3fb1609, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 754d3b33bb2579e3a5053acafafd2e5d146a36c17e4a960278f05bd870389f64
- TakerPaymentSent · TakerPaymentReceived: 4bf7d575ead8ba0b67e8c7ba2b624f408cf7a5e3549108c7e231408d94979022
- TakerPaymentSpent: c8b47530d8b89f222ed497956423597b424fb9c879a2f28763616558613c364b
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.