← previous blocknext block →recent activity
Analyzing
Block #87,576,315
17 transactions · 16 stateful · 2026-07-13 22:42:04 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,576,315 · 17 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
1w02w13w05w16w28w09w111w212w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0x925c118c…a1d8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x79e62da8…efdc
0x34b655…2a6f
6 touches
3 conflicts
0x44b83187…fd48
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0x59876ddf…4166
0x34b655…2a6f
4 touches
1 conflict
0x5e0f04a0…1478
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 0xca608d0ccc…6ff23b
Audit this contract →
← previous block·next block →recent activity