← previous blocknext block →recent activity
Analyzing
Block #96,491,014
13 transactions · 12 stateful · 2026-08-16 12:34:25 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,491,014 · 13 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
1w03w04w05w18w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9ab6fca5…de5c
0x34b655…2a6f
8 touches
6 conflicts
0xbffde283…3385
0x34b655…2a6f
6 touches
3 conflicts
0xc87e767e…4bba
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
10 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity