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.
e267e0fa1335e3f4ea45796a0415306af51c11c301ecf80c188989796ab8f92c
Both payments are on their chains and locked to the same secret hash 81c829704509ed2d3e81056f555e2295cee557a7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e267e0fa1335e3f4ea45796a0415306af51c11c301ecf80c188989796ab8f92c
- MakerPaymentSpent: 519a5e697fe5712fbc825602fd99e61e656c5f39b9b3662368d5a30434c74df5
ef6bccaeccf19b2062612e9f9a2391d10ec6c11f16404b61bd1276fe4bf83715
Both payments are on their chains and locked to the same secret hash 81c829704509ed2d3e81056f555e2295cee557a7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 851064a8159e80960c21e170a51c5b8ba2080e391f9ece55d46c1ed2da9a6d91
- TakerPaymentReceived · TakerPaymentSent: ef6bccaeccf19b2062612e9f9a2391d10ec6c11f16404b61bd1276fe4bf83715
- TakerPaymentSpent: 0cbb5a2f933601151237a7438dc7dbda6bd50edc0bfc21c3fd73e54a793cc71b
Reported by kdf-statsdb-8762.