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.
1351020bd29018baea8767a8dbf402611c4dae1826f7075b71526303beb74a41
Both payments are on their chains and locked to the same secret hash 32dff4daf87d9f933fa3694b75500e72d9e08553, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1351020bd29018baea8767a8dbf402611c4dae1826f7075b71526303beb74a41
- MakerPaymentSpent: ef498aa9e65666f42608fce89d1dcd9db894ba0593e96eec0cc222de560fc3bf
a7d4a2af92f6d22cd3c3f7fd41f28af04369fc17130cedaa5442e22cfcc7874d
Both payments are on their chains and locked to the same secret hash 32dff4daf87d9f933fa3694b75500e72d9e08553, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aa94a31473410e16e3945cde963e836513ba2392b4d09b98fb0a089e5c973d7e
- TakerPaymentSent · TakerPaymentReceived: a7d4a2af92f6d22cd3c3f7fd41f28af04369fc17130cedaa5442e22cfcc7874d
- TakerPaymentSpent: b11add6586d360889104b92af14f0057255c44b6fdb58a86b43497050f6a6c6e
Reported by kdf-statsdb.