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.
56193729064e3298b2da90287ef9cf8e16bbc18dc8b2ed3747a6eae881162aa3
Both payments are on their chains and locked to the same secret hash 17903924c22f1066a55b2178df5cc9b210759f37, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 56193729064e3298b2da90287ef9cf8e16bbc18dc8b2ed3747a6eae881162aa3
- MakerPaymentSpent: 97c83a6505cdbe9ac1b68ee9b3aaa8439096a8dc48ccb36b645c8448cad72ba3
11cad0e84fba3eef430460ba4b27948581f32ad49a11a672ade02dbfa572b100
Both payments are on their chains and locked to the same secret hash 17903924c22f1066a55b2178df5cc9b210759f37, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3aa4c56bafb600f946f71963977302149cc0b60127f4fc34abcf30efd2e3e665
- TakerPaymentSent · TakerPaymentReceived: 11cad0e84fba3eef430460ba4b27948581f32ad49a11a672ade02dbfa572b100
- TakerPaymentSpent: ea76c3c4ed6b463b8499e9b903391fa7a0e6e3cc935483e55584d1c65b52d165
Reported by kdf-statsdb-8762.