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.
b9b70f9076e34ec314ad88a7bc56ff0b2dbd22d8b961b55013979e6b66677cfa
Both payments are on their chains and locked to the same secret hash 185d0d0fb511960d144935fb64ceefbebc0705ec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b9b70f9076e34ec314ad88a7bc56ff0b2dbd22d8b961b55013979e6b66677cfa
- MakerPaymentSpent: c4a414cfd693b1ff1b7ac970385727d625cdf5eeb6714f60dcf3661717f9bac9
22e2b8a79337d6e25e1dfe808e56da008e8813bc7f4ca6cabc892d964e16fc63
Both payments are on their chains and locked to the same secret hash 185d0d0fb511960d144935fb64ceefbebc0705ec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: feeb6928379e1b29ae1918931854058e6c0f651253ef550387fe474ba9288038
- TakerPaymentSent · TakerPaymentReceived: 22e2b8a79337d6e25e1dfe808e56da008e8813bc7f4ca6cabc892d964e16fc63
- TakerPaymentSpent: 95e1f92d423e1a21bcc3f8807020aabe3e8fcdfb341775de07d4c5415aa67c48
Reported by kdf-statsdb.