← previous blocknext block →recent activity
Analyzing
Block #87,587,667
21 transactions · 21 stateful · 2026-07-13 23:58:00 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,587,667 · 21 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
1w02w13w04w16w07w19w210w311w417w518w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8fec9ca…2d60
0x34b655…2a6f
12 touches
15 conflicts
0x09afe8a8…2c17
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x1175233a…64e7
0x34b655…2a6f
10 touches
10 conflicts
0x2efc4b1d…474b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xc8fec9cacc…f42d60
Audit this contract →
← previous block·next block →recent activity