← previous blocknext block →recent activity
Analyzing
Block #96,031,233
11 transactions · 10 stateful · 2026-08-14 22:01:50 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,031,233 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b77
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xb64a26cd…4ffa
0x34b655…2a6f
4 touches
1 conflict
0x3939eef2…95ad
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x201986e4…c48c
0x34b655…2a6f
4 touches
1 conflict
0xc2e7dadf…f0a2
0x34b655…2a6f
3 touches
1 conflict
0x4164abbf…e433
0x34b655…2a6f
3 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
1 conflict on slot 0x6d1b72eefe…416b77
Audit this contract →
← previous block·next block →recent activity