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.
28459390be0992f0d9775e771c2185863773c4476f0c81c9f9c96d68f915a8f1
Both payments are on their chains and locked to the same secret hash 4af69f76d477571caca610b744a90c3e4b049c8b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 28459390be0992f0d9775e771c2185863773c4476f0c81c9f9c96d68f915a8f1
- MakerPaymentReceived · 28459390be0992f0d9775e771c2185863773c4476f0c81c9f9c96d68f915a8f1
- MakerPaymentSpent · 2a9034434700b8724a63c232f6d0b5fd13adba83df78bebe739b21ed140c20fb
585da10eec2321f12df302b60ae79f290b503f1a54388ed85c1b6f81edbc7e48
Both payments are on their chains and locked to the same secret hash 4af69f76d477571caca610b744a90c3e4b049c8b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 408de01dea91323dad686ad8ac246da532b38b533656b83a3495ef0e18bc42bf
- TakerPaymentReceived · 585da10eec2321f12df302b60ae79f290b503f1a54388ed85c1b6f81edbc7e48
- TakerPaymentSpent · a4d3fc56709d55641388231c09b2653072c2812fcfe2da6b9b621927dfe39a99
- TakerFeeSent · 408de01dea91323dad686ad8ac246da532b38b533656b83a3495ef0e18bc42bf
- TakerPaymentSent · 585da10eec2321f12df302b60ae79f290b503f1a54388ed85c1b6f81edbc7e48
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.