← previous blocknext block →recent activity
Analyzing
Block #87,756,404
25 transactions · 23 stateful · 2026-07-14 18:46:35 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,756,404 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w28w310w111w412w213w514w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x0d42a59b…df19
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xcb76b2ed…89a5
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x40883ce5…2ae2
0x34b655…2a6f
6 touches
3 conflicts
0x48260180…a411
0x34b655…2a6f
6 touches
3 conflicts
0x48260180…a412
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity