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.
04b6bbba86c9e99706383dbd417b43e4780c87f1129760165a1ca202dc02d8e7
Both payments are on their chains and locked to the same secret hash 06426b1e96979dde132eaa67cd727e408f0ba75c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 04b6bbba86c9e99706383dbd417b43e4780c87f1129760165a1ca202dc02d8e7
- MakerPaymentSpent: 106bdd09efd9aaef0dc4e0957fefc9fd862ad2e5072485c32d85fd13af45ef7e
a5de18ad7a8d05cfa6f979a71715fe3844ce362c600806dff535b4da3c3c7291
Both payments are on their chains and locked to the same secret hash 06426b1e96979dde132eaa67cd727e408f0ba75c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ef6c0ad09ecfe95ad4823e37c526f3410f09eaf85ede0d3950ec46484a9855fb
- TakerPaymentSent · TakerPaymentReceived: a5de18ad7a8d05cfa6f979a71715fe3844ce362c600806dff535b4da3c3c7291
- TakerPaymentSpent: 7e9a21d6fe9b29634d52796472cf283e3eea849dceeb8404bb48a22e499ffef2
Reported by kdf-statsdb.