← previous blocknext block →recent activity
Analyzing
Block #99,320,658
32 transactions · 23 stateful · 2026-08-26 11:46:39 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,320,658 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w017w018w419w125w426w230w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d43ee99…bdd8
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x86efd4ce…04b5
0xd32edf…ff58
9 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: ShMonad (shMON)
10 conflicts on slot 0x6d43ee99c8…ecbdd8
Audit this contract →
← previous block·next block →recent activity