We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Only 8 ordinals returned of the 73 on an address. Is this related to an indexing error?
Transaction ID n.a. Address bc1p04vqcelrdtm8kjp23redj9h073n7mp778tx03pe3sh2tzsw9gyys63q34t Block# n.a. Time stamp n.a.
To Reproduce The user noticed their Leather doesn't show all the inscriptions which is also apparent from the ordinals explorer: https://ordinals.hiro.so/address/bc1p04vqcelrdtm8kjp23redj9h073n7mp778tx03pe3sh2tzsw9gyys63q34t (8 ordinal inscriptions displayed).
When compared to:
https://www.ord.io/bc1p04vqcelrdtm8kjp23redj9h073n7mp778tx03pe3sh2tzsw9gyys63q34t (73 inscriptions shown)
Expected behavior We expect all 73 inscriptions to be displayed.
Screenshots Hiro explorer
Ord
The text was updated successfully, but these errors were encountered:
Thanks for the report -- should be fixed now 🚀
Sorry, something went wrong.
janniks
No branches or pull requests
Describe the bug
Only 8 ordinals returned of the 73 on an address. Is this related to an indexing error?
Transaction ID n.a.
Address bc1p04vqcelrdtm8kjp23redj9h073n7mp778tx03pe3sh2tzsw9gyys63q34t
Block# n.a.
Time stamp n.a.
To Reproduce
The user noticed their Leather doesn't show all the inscriptions which is also apparent from the ordinals explorer: https://ordinals.hiro.so/address/bc1p04vqcelrdtm8kjp23redj9h073n7mp778tx03pe3sh2tzsw9gyys63q34t (8 ordinal inscriptions displayed).
When compared to:
https://www.ord.io/bc1p04vqcelrdtm8kjp23redj9h073n7mp778tx03pe3sh2tzsw9gyys63q34t (73 inscriptions shown)
Expected behavior
We expect all 73 inscriptions to be displayed.
Screenshots
Hiro explorer
Ord
The text was updated successfully, but these errors were encountered: