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.
0338dbc39bd3ab652b9274d0cd7e44adfdf0ce4db39e74b98854fd352593e31a
Both payments are on their chains and locked to the same secret hash 57bcb68a9004305257eb9be85f347a99ff4ffc76, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0338dbc39bd3ab652b9274d0cd7e44adfdf0ce4db39e74b98854fd352593e31a
- MakerPaymentSpent: 3d27a4ddf830b565dc0070865351eefe04b2e9cdb53f1385b78d0f217d08fe08
25b0852be3456b1781c7139ac7681639b53becd60a1aef08dcfc82ac566e0b5a
Both payments are on their chains and locked to the same secret hash 57bcb68a9004305257eb9be85f347a99ff4ffc76, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58992084876ca3a22e019dcfde79ac0e266dc6772b4823d242d19a98fa5d5ecc
- TakerPaymentSent · TakerPaymentReceived: 25b0852be3456b1781c7139ac7681639b53becd60a1aef08dcfc82ac566e0b5a
- TakerPaymentSpent: 0019536c2eb5bcff2ec78c6401dd48e5364b38e0995268e811e725ca46537cd4
Reported by kdf-statsdb-8762.