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