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.
4f000753ef9656b0e5bf71f3858bd6e746a3c9be70e4e20ac2b8848d0028176d
Both payments are on their chains and locked to the same secret hash 731f987086cab7ffe69da951c5ba0215d97597bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4f000753ef9656b0e5bf71f3858bd6e746a3c9be70e4e20ac2b8848d0028176d
- MakerPaymentReceived · 4f000753ef9656b0e5bf71f3858bd6e746a3c9be70e4e20ac2b8848d0028176d
- MakerPaymentSpent · a29b544e40cd8f8228471143b3f11742765469eab030ce6f1cf72a7c4b780535
98f751695856b73168f1e630a1b5176b8fedd5a20f26651e3c24c233a089ce73
Both payments are on their chains and locked to the same secret hash 731f987086cab7ffe69da951c5ba0215d97597bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 5af1b1ff58b1f8a1412c56ee838d81706121111d3c364842fa0a3a9884780a38
- TakerPaymentReceived · 98f751695856b73168f1e630a1b5176b8fedd5a20f26651e3c24c233a089ce73
- TakerPaymentSpent · ffbfdd27337014419f1aa988df05eec810e3c3079ab0449487629b0e8ee0d2ce
- TakerFeeSent · 5af1b1ff58b1f8a1412c56ee838d81706121111d3c364842fa0a3a9884780a38
- TakerPaymentSent · 98f751695856b73168f1e630a1b5176b8fedd5a20f26651e3c24c233a089ce73
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.