← previous blocknext block →recent activity
Analyzing
Block #87,593,004
22 transactions · 19 stateful · 2026-07-14 00:33:42 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,593,004 · 22 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
1w02w13w07w09w110w211w315w016w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
6 touches
3 conflicts
0x21158693…63e2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x2d9375da…b617
0x34b655…2a6f
4 touches
1 conflict
0x41fffe57…5434
0x34b655…2a6f
4 touches
1 conflict
0x4467ecee…e95b
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity