We just launched the first #Algorand Blockchain analysis tool:
https://t.co/uaoUE8PUFB
Enter any address and find out, in aggregate and per each peer address:
🔄 $ALGO inflows/outflows/net
🔢 # of transactions
📅 Dates first/last transacted
1/5
@algo_surf updated, featuring information that is usually not captured by indexers. First, we have metrics like TPS and fees over time. Drag over the chart to zoom in, or explore any time slice from the presets and Period dropdown. You can get to the exact blocks by clicking block bars.
It is fun to click around and find TPS spikes - here are some TPS examples from my+@Urthoo's May 2024 ALGO+USDC load tests:
https://t.co/8j7mtYoCFA
https://t.co/7H9qHBczka
This is powered by surf-indexer, a new (unofficial) indexer that supplements data left out by the official one. It uses DuckDB and currently takes up just 750MB for the Mainnet data set. It is pretty fast at what it does, currently being served live (no cache) from a potato VPS and a laptop. You can see code and features here: https://t.co/hupuJGLYnA
There's a bunch of other features for you to discover around accounts. One of my favorites is the relationship between multisig accounts and sub-signers. Normally this relationship is only discoverable one-way (from multisig to sub-signer)
Now, for each account, you can see which multisigs they are a part of, as well as whether they have ever signed or not (as listing sub-signers is permissionless, so if an account hasn't signed for a multisig, they may not have been aware that they were part of it)
https://t.co/CIli9HN8Xw
There's also semi-hidden work on logic sigs, pending a bit of polish and labeling💅
Finally a topical one: there's a Consensus Upgrades page, which lists all consensus upgrades that have taken place. https://t.co/8pK67TwVZG
Which brings me nicely to: Upgrade your nodes, algod 5.0.4 is out with a new consensus release.
Try searching for a transaction on the wrong network
Like this: https://t.co/cxAzVKyq5e
For all you devs out there who have more tabs open than llm token budget
Actually it's already here and have been for two days, just haven't had time to make a nice promo, but I will. Meanwhile connect your midi gadget and set up up to eight channels.
And then it's 0.001A - the min fee, per tone. And anyone can hear it on the other end of the ledger (づ ᴗ _ᴗ)づ♡
https://t.co/PJSDD8i6I8 will now warn if you've viewing a transaction involving a... nonexistent asset.
Yes, you can write anything in the asset ID if you send zero amount of it 🥵
Thanks @hampelman_data my cortisol almost dropped to healthy range for a few hours
Algorand consensus v42, a.k.a. Algorand v5.0 protocol, has just passed consensus vote with 9,198 / 10,000 🥳
You can see the passing vote results here: https://t.co/l7qGyqjOmw
The protocol upgrade will automatically take effect at round 64318659 - give or take a week from now🎉
@LoafPickle Yes. Accounts that have not sent transactions are "unknown". You don't know if the address corresponds to an ED25519 public key, or multisig config hash, or a pq account hash, etc
- @algo_surf vote yes/no bars now race from their respective sides to the 90% threshold white mark (1)
- Details view cleaned up (2)
- Fixed error affecting US east region (3)
Let's go v5! ~84% of node runners have upgraded, 90% needed
"Wen upgrade?"
You can now follow protocol upgrade voting progress on your 3rd favorite algorand explorer
- Voting progress
- Voting close ETA
- New version features
clerk•algo•surf got a performance overhaul! Export your ALGO and ASA transactions to CSV at blinding speeds.
83 sec > 7 sec⚡
- NFD support
- Application Escrow support
- Time Ranges (last day, week, etc)
Your Algorand wallet is probably full of dust.
Dead tokens. Micro balances. Each one locking up 0.1 ALGO in MBR.
We just shipped the Dust Sweeper to clean it all up 🧹🧵