← previous blocknext block →recent activity
Analyzing
Block #87,052,602
20 transactions · 19 stateful · 2026-07-11 12:19:04 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,052,602 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w29w312w414w115w217w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x9199a85a…acd9
0x34b655…2a6f
10 touches
10 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
6 touches
3 conflicts
0x5e67eb31…015a
0x34b655…2a6f
6 touches
3 conflicts
0x5e67eb31…015b
0x34b655…2a6f
6 touches
3 conflicts
0x236b16bf…ea47
0x34b655…2a6f
6 touches
3 conflicts
0x219c6953…c961
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity