← previous blocknext block →recent activity
Analyzing
Block #87,667,021
52 transactions · 40 stateful · 2026-07-14 08:48:28 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
2.1
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,667,021 · 52 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w411w012w113w014w115w218w020w121w222w335w236w439w1040w542w643w448w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
14 touches
21 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
12 touches
15 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
12 touches
15 conflicts
0x9fd37234…2731
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
36 conflicts on slot 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity