[explorer.moveonLibra.com]: Yet Another Opensource Libra Blockchain Explorer

Hello everyone,

It’s a pleasure to announce our Libra blockchain explorer “MOL LibraExplorer”.

A Realtime Libra Blockchain Explorer

There are several Libra explorers there already. For example, libexplorer.com and
Libraview.org both are pretty good. Why write another Libra Explorer?

Because all these explorers are not realtime. They pull data from Libra blockchian and save it to their own private database. When you access their explorer website, they search data from private database and return data to you.

On the other hand, MOL LibraExplorer fetch data from original Libra blockchain in realtime and return data to you. So, the data is more accurate and fresher. You can access the Libra testnet blockchain data by visiting following website:


It’s fast and accurate. You can also see the raw json data which provide more details.

Support Third-party Libra Network

“MOL LibraExplorer” can support any third-party Libra network as long as the host and port of those network is publicly accessible. The easiest way to browser a third-party libra network is prefix the host and port to “explorer.moveonlibra.com” with following syntax:


for example, There is a libra-swarm network started by run:

cargo run -p libra-swarm

and the host and port are “” and “33333” respectively. So you can brower the blockchain data on this network by open this url:

We will add more formal method to support third-party Libra network. Currently, you cann’t mint coin and commit transactions on these third-party Libra network explorer.

That’s what we’re doing right now. The source code is here: LibraExplorer Source

Any feedback is welcome.


It’s fascinating! thanks a lot

1 Like

I can’t visit explorer.moveonlibra.com , maybe the website is down?

1 Like

It seems the Libra testnet is down. Anyone has similar problem?

$ ./scripts/cli/start_cli_testnet.sh

Not able to connect to validator at ac.testnet.libra.org:8000, error RpcFailure(RpcStatus { status: RpcStatusCode(4
), details: Some(“Deadline Exceeded”) })

It seems that Libra testnet has just restarted.

The testnet server may be unstable again? :woozy_face:

MOL Explorer has some updates:

1. Libra Network Selector

“MOL LibraExplorer” support three types of libra blockchain network:

  • Testnet, official libra blockchain network for test, operated by Libra Association.

  • Devnet, a specail version of testnet maintained by MoveOnLibra instead of Libra Association, support publish and execute custom move modules and scripts.

  • Anonymous, any third-party Libra network as long as the host and the admission control port of those networks are publicly accessible.

The Select Network feature let’s you select one of the supported networks to explore.

2. Show Error Message For Execution Failed Transactions

Show Error Message In the Transaction List Page:

Show Error Code and Error Message In the Single Transaction Show Page:

3. Some Transaction Loading optimization

You can navigate transactions even in the transaction show page with First, Prev, Next and Last transaction link.

1 Like

MOL explorer now support multi-languages:

Screen shot of the simplified chinese website:

Screen shot of the japanese website:


We need your help to translate the MOL explorer to more languages, such as German, French, Korean, Spanish etc.

The translation file is here:


MOL LibraExplorer is updated with latest Testnet.

There are too many BlockMetadata transactions.


Thank you for providing this awsome blockchain explorer.

Yes, on the CLI as well. No transactions are visible

Through Libra Association Address,you can see some real transactions:


q tr 1 1 true on the CLI that is included only returns blockmetadata

Yes, for new versions you get a “correct” response. But the balances etc of addresses are reset while the versions are not. Meaning that nothing is as it should right now

“q tr 1 1 true” get the version 1 transaction which is BlockMetadata now.
The first SingedTransaction seems to be version 8499:

libra% q tr 8499 1 true

The current blockmetadata reponses are impossible to work with. I hop it is not by design :nerd_face:

Agree with you, too many BlockMetadata .

But you already fixed it I see. Good one. We are implementing a fix right now. Besides the blockmetadata everything else seems to be working

What these kinds of transactions are for, sir? :thinking: