← previous blocknext block →recent activity
Analyzing
Block #87,750,142
28 transactions · 23 stateful · 2026-07-14 18:04:44 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,750,142 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w112w214w315w422w324w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf2112d98…bb04
0x34b655…2a6f
6 touches
3 conflicts
0x7ab016af…dae9
0x34b655…2a6f
6 touches
3 conflicts
0x44f21d75…6279
0x34b655…2a6f
4 touches
1 conflict
0x5b353877…605d
0x34b655…2a6f
4 touches
1 conflict
0x644217c2…d61e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity