Inspiration

One day I visited https://explorer.near.org/ to see the history of transactions for my account. I wanted to know the date when I transferred some specific fungible token to another specific account. Unfortunately, it was not a simple task, since explorer shows fungible token transactions (and many others) as 'method calls'. Plus, the contract of the token I was looking for doesn't contain token name, so I couldn't just CTRL+F for it. Finally it took me some time to find the transaction I was looking for. So this is the moment when I came with the idea of Keek(e)r.

What it does

Keekr shows you 'method call' transactions in more human friendly way, than current version of explorer.near.org. It also allows you to filter transaction list. I.e. you can browse only transactions related for a specific token or the NFT contract. See details at: https://github.com/sinyavsky/keeker#what-exact-problem-does-keekr-solve

How I built it

I had no experience with NEAR ecosystem as developer, so it took me some time to read the docs / discord / telegram chats and find the information that I needed to build an application.

Challenges I ran into

I didn't have enough experience with app building before. This is the second app I was making and the first app I was making without any mentorship. So the most hard part for me was to build the whole project architecture, so I won't drown in the amount of code I write. There is still a lot of code that should be refactored though.

Accomplishments that I'm proud of

Well, I did some working product by myself without any help, yay :) It's not perfect, there are still a lot of work to be done, but a start has been made.

What I learned

Most important is that now I have more knowledge about the NEAR ecosystem, since I've spend a lot of time reading documentation and searching for answers in NEAR community chats. I even made few tiny pull requests to https://github.com/near/docs/ that already have been merged to master. That was my first experience in contributing to open source and it feels great.

What's next for Keekr

Right now it's a very primitive application. In a long term I would like to extend it's functionality so it will be some sort of hub, where you can get all possible information about NEAR account (FT balances, NFTs, trading history and so on). And all this information will be in a human friendly way (this is the key point), so everyone will be able to use it. Short-term plans:

  • Huge code refactoring (probably will use React)
  • Deeper function call recognition for NFT contracts
  • Support of the function call recognition for more popular contracts
  • Server-side caching
  • UI/UX improvements

Built With

Share this project:

Updates