← previous blocknext block →recent activity
Analyzing
Block #96,039,294
9 transactions · 8 stateful · 2026-08-14 22:42:24 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,039,294 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf0f3352…1fd9
0x34b655…2a6f
4 touches
1 conflict
0xdc0e94cb…c6d5
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x036adc97…48eb
0x34b655…2a6f
2 touches
0 conflicts
0x14d9e0d5…29cc
0x34b655…2a6f
2 touches
0 conflicts
0x4174fdf9…fcfd
0x34b655…2a6f
2 touches
0 conflicts
0x52e88fc2…bbcf
0x34b655…2a6f
2 touches
0 conflicts
0x66401d81…7a05
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0xcf0f335237…b61fd9
Audit this contract →
← previous block·next block →recent activity