← previous blocknext block →recent activity
Analyzing
Block #101,991,235
8 transactions · 8 stateful · 2026-09-04 20:07:33 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,991,235 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5d0cbe9…5172
0x34b655…2a6f
6 touches
3 conflicts
0x7d619bb4…a65c
0x34b655…2a6f
6 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x583a521d…ae3a
0x34b655…2a6f
2 touches
0 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
2 touches
0 conflicts
0x7c3ee46f…a8f4
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
3 conflicts on slot 0xc5d0cbe9d6…9c5172
Audit this contract →
← previous block·next block →recent activity