← previous blocknext block →recent activity
Analyzing
Block #87,717,330
17 transactions · 14 stateful · 2026-07-14 14:25:14 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,717,330 · 17 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
2w03w18w09w110w212w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa629d950…36f6
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x58126412…4dad
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4da2c807…8775
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
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
10 conflicts on slot 0xa629d950d8…d936f6
Audit this contract →
← previous block·next block →recent activity