Dmytro
Dmytro
***Describe the bug*** Wrong `blockId` field in [BlockReference]([https://github.com/near/near-api-js/blob/master/src/providers/provider.ts#L35](https://github.com/near/near-api-js/blob/master/src/providers/provider.ts#L35)) type for [Provider.query]([https://github.com/near/near-api-js/blob/master/src/providers/provider.ts#L416](https://github.com/near/near-api-js/blob/master/src/providers/provider.ts#L416)) method. ***To Reproduce*** Steps to reproduce the behavior: 1\. Write some `query` method, and pass `blockId` and execute it:...
## Story As a USER who views [https://explorer.near.org/nodes/validators](https://explorer.near.org/nodes/validators) in Vietnamese, I want to see all terms in my native language so I can better understand what the metrics is and...
## Story As a USER who want to see all transaction details, I want to see some placeholders or loaders when there is still no data so I can understand...
## Story As a USER who using Explorer and explore metrics of network, I want to see numbers in shorter format so I can easily understand their meaning. ## Acceptance...
## Story As a USER who use search, I want to se the result of searching so I can easily find something I want to. Recently we had an issue...
## Story On the explorer side we [collect](https://github.com/near/near-explorer/blob/master/frontend/src/pages/api/nodes.ts#L17) telemetry information about validator and [write](https://github.com/near/near-explorer/blob/master/backend/src/wamp.js#L29) it to [analytics](https://github.com/near/near-analytics) database. We do it for every validator separately, but because of a lot...
Closes https://nearinc.atlassian.net/browse/DEC-528