← previous blocknext block →recent activity
Analyzing
Block #101,989,006
18 transactions · 16 stateful · 2026-09-04 19:56:11 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,989,006 · 18 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
1w02w13w24w35w48w011w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d28bce…c32c
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0x79ec4509…1f61
0x34b655…2a6f
6 touches
3 conflicts
0x7c216fca…20cb
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x8feb2121…031a
0x34b655…2a6f
6 touches
3 conflicts
0x999c658d…b185
0x34b655…2a6f
6 touches
3 conflicts
0x9d7ac3b9…22f8
0x34b655…2a6f
6 touches
3 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 0xf5d28bce28…fbc32c
Audit this contract →
← previous block·next block →recent activity