← previous blocknext block →recent activity
Analyzing
Block #87,498,986
20 transactions · 19 stateful · 2026-07-13 14:04:06 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,498,986 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w211w212w313w414w516w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe021dbc8…d27b
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3c7908ed…47c8
0x34b655…2a6f
6 touches
3 conflicts
0x1353affc…75e0
0x34b655…2a6f
6 touches
3 conflicts
0x701208a7…46b3
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xe021dbc877…acd27b
Audit this contract →
← previous block·next block →recent activity