← previous blocknext block →recent activity
Analyzing
Block #87,717,868
14 transactions · 13 stateful · 2026-07-14 14:28:50 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,717,868 · 14 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
1w02w13w04w25w36w49w511w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xff2c0517…acf7
0x34b655…2a6f
6 touches
3 conflicts
0x24d58d14…f7a5
0x34b655…2a6f
6 touches
3 conflicts
0x3e950538…2259
0x34b655…2a6f
6 touches
3 conflicts
0x5c79a7db…b7aa
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
10 conflicts on slot 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity