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.
9b32f844d8f5f67698f69e9e42ecc2e41ad2c226502fccd016819088840ee181
Both payments are on their chains and locked to the same secret hash d76e2ddd6290c78ed174fc3d1b93e4f70e7d826c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 9b32f844d8f5f67698f69e9e42ecc2e41ad2c226502fccd016819088840ee181
- MakerPaymentReceived · 9b32f844d8f5f67698f69e9e42ecc2e41ad2c226502fccd016819088840ee181
- MakerPaymentSpent · 3f129bfc0f9318ef52e7befdfe05b37fca79bafabc7c0b70cea156621ea1bb82
38f1744001e4c661116dd6f6f0cff4b0fc66efaba84438f1bcdf404bc38718f9
Both payments are on their chains and locked to the same secret hash d76e2ddd6290c78ed174fc3d1b93e4f70e7d826c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · dfcd879f42a8b00dff815eb36dbc5cb74ba7bd3853c8fcb229de52f79ff793cb
- TakerPaymentReceived · 38f1744001e4c661116dd6f6f0cff4b0fc66efaba84438f1bcdf404bc38718f9
- TakerPaymentSpent · c72ec589b8d5fe8ee6e1c4e8c4bce235733f0438cd303928159feb4a786f4742
- TakerFeeSent · dfcd879f42a8b00dff815eb36dbc5cb74ba7bd3853c8fcb229de52f79ff793cb
- TakerPaymentSent · 38f1744001e4c661116dd6f6f0cff4b0fc66efaba84438f1bcdf404bc38718f9
Reported by kdf-statsdb.