it's very difficult / dangerous to make comparison like this. What are you comparing to? dozens of hashes against 1 hash, cost factor 5 (2^5 = 32) against cost factor 19 (2^19 = 524288 "iterations").
Since it's parameterized with a flexible cost factor settings, you can't really make fair comparisons: apple to oranges.
bcrypt is a very hard to crack hashing type, because of the design of this slow hash type that makes it memory hard and GPU-unfriendly (especially with high cost factors).
In cases like this I would really suggest to take a step back, try to understand what the cost factor of your hashes is, try to crack a simple generated test and see how long you take to crack 1 single test with similar cost factor for which you have the password etc.
I don't think in these types of situations it's very common that there is something "wrong"... it's most of the time just a misunderstanding or missing knowledge about the details of the hashing algorithms and how the parameters (cost factor) and algo work etc
Since it's parameterized with a flexible cost factor settings, you can't really make fair comparisons: apple to oranges.
bcrypt is a very hard to crack hashing type, because of the design of this slow hash type that makes it memory hard and GPU-unfriendly (especially with high cost factors).
In cases like this I would really suggest to take a step back, try to understand what the cost factor of your hashes is, try to crack a simple generated test and see how long you take to crack 1 single test with similar cost factor for which you have the password etc.
I don't think in these types of situations it's very common that there is something "wrong"... it's most of the time just a misunderstanding or missing knowledge about the details of the hashing algorithms and how the parameters (cost factor) and algo work etc