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.
e31940293b82474dd38ab25fc4c0d403a36db55e355a03f8e16ccd60ed0a545f
Both payments are on their chains and locked to the same secret hash e1e57bb9f10e768b7488bc3b6d4fe70680eb105d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e31940293b82474dd38ab25fc4c0d403a36db55e355a03f8e16ccd60ed0a545f
- MakerPaymentSpent: 285f79b1069af2c04d7703950199b60229d8d4e222ecd20367b33aac69e58698
cc51bea13a900d7e82ac601c62825fb7dd10f5c4c9bafde9c46f284b9724d9b6
Both payments are on their chains and locked to the same secret hash e1e57bb9f10e768b7488bc3b6d4fe70680eb105d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3b79f319387d294e91ad2f19c87b3de43bc433ff1fd683bcfcab80e4272dcc62
- TakerPaymentReceived · TakerPaymentSent: cc51bea13a900d7e82ac601c62825fb7dd10f5c4c9bafde9c46f284b9724d9b6
- TakerPaymentSpent: 6f9a7c21685ce5080aa7b8d3e8002d8149f0c41e1b9c359e2d0eb75c03fed2fe
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.