← previous blocknext block →recent activity
Analyzing
Block #87,731,738
20 transactions · 18 stateful · 2026-07-14 16:01:36 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,731,738 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w110w211w312w413w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4de6652…13f4
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x91d48be7…e4e8
0x34b655…2a6f
12 touches
15 conflicts
0xbabe821d…939b
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0xff14a3fd…80bc
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
21 conflicts on slot 0xc4de665222…6513f4
Audit this contract →
← previous block·next block →recent activity