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.
4ed936cda2f89bbf8bdc3d2529414bccb6608a100ebdf85378ac82bf21226bd3
Both payments are on their chains and locked to the same secret hash e9618a333d7190fce9943f8181c0338cdf7aa382, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4ed936cda2f89bbf8bdc3d2529414bccb6608a100ebdf85378ac82bf21226bd3
- MakerPaymentSpent: b12a353bc893b114d61ff54279f8cfac5bdab0f4fa42c5ae4d47719435e57d95
8a55e514d7e3ce15f96e9cc8042ac569788fc86442655bc41c1b55c7178ceb8a
Both payments are on their chains and locked to the same secret hash e9618a333d7190fce9943f8181c0338cdf7aa382, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4a7208d545fb2ae25cab06c846d77b4932770db151fe7a1c3472739c5b84616f
- TakerPaymentSent · TakerPaymentReceived: 8a55e514d7e3ce15f96e9cc8042ac569788fc86442655bc41c1b55c7178ceb8a
- TakerPaymentSpent: 68969cf76ec3cac7fa114bf3afe86e59afc57a75ba532e12466f55a5d811db96
Reported by kdf-statsdb.