← previous blocknext block →recent activity
Analyzing
Block #86,633,351
20 transactions · 16 stateful · 2026-07-09 13:36:32 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,633,351 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w18w09w210w013w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d22c439…de6d
0x34b655…2a6f
6 touches
3 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
6 touches
3 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
6 touches
3 conflicts
0x5f72d58f…c445
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
6 touches
3 conflicts
0x74fce6ad…7895
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
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
3 conflicts on slot 0x3d22c43954…e7de6d
Audit this contract →
← previous block·next block →recent activity