← previous blocknext block →recent activity
Analyzing
Block #87,756,681
20 transactions · 17 stateful · 2026-07-14 18:48:26 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,756,681 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w19w210w212w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfb7adca…51d7
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe954af0e…b8f3
0x34b655…2a6f
6 touches
3 conflicts
0xed7d2f2e…4b9d
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xbfb7adcac2…1751d7
Audit this contract →
← previous block·next block →recent activity