← previous blocknext block →recent activity
Analyzing
Block #87,592,561
26 transactions · 21 stateful · 2026-07-14 00:30:44 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.27
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,592,561 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w512w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x63f8a50d…333b
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x0ba865dd…a249
0x34b655…2a6f
12 touches
15 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
12 touches
15 conflicts
0x548145a9…cfce
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
12 touches
15 conflicts
0x0744cdb7…37be
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity