← previous blocknext block →recent activity
Analyzing
Block #87,732,235
18 transactions · 17 stateful · 2026-07-14 16:04:56 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,732,235 · 18 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
1w02w15w06w07w19w110w211w212w315w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68761f35…6026
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x4cee015b…1a5e
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x3a1edb3e…b841
0x34b655…2a6f
6 touches
3 conflicts
0x5eb5d9be…b2c1
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
6 conflicts on slot 0x68761f355d…c46026
Audit this contract →
← previous block·next block →recent activity