← previous blocknext block →recent activity
Analyzing
Block #86,634,300
23 transactions · 21 stateful · 2026-07-09 13:42:53 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,634,300 · 23 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
2w03w16w07w19w011w212w216w017w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3983648…392f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4572c9a0…5cf9
0x34b655…2a6f
4 touches
2 conflicts
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x81e10884…13f0
0x34b655…2a6f
4 touches
1 conflict
0x9d8e8317…636e
0x34b655…2a6f
4 touches
1 conflict
0xada5ad75…1d24
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 0xe398364807…32392f
Audit this contract →
← previous block·next block →recent activity