← previous blocknext block →recent activity
Analyzing
Block #87,754,761
18 transactions · 16 stateful · 2026-07-14 18:35:37 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,754,761 · 18 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
2w03w14w25w36w49w010w111w216w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc99e7125…81b1
0x34b655…2a6f
12 touches
15 conflicts
0x388633a0…86cd
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x2f702750…347d
0x34b655…2a6f
8 touches
6 conflicts
0x70b90757…51be
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
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
15 conflicts on slot 0xc99e71253c…e381b1
Audit this contract →
← previous block·next block →recent activity