← previous blocknext block →recent activity
Analyzing
Block #87,682,791
20 transactions · 19 stateful · 2026-07-14 10:33:51 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,682,791 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w18w29w310w413w214w216w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x91d48be7…e4e8
0x34b655…2a6f
6 touches
3 conflicts
0xbfc73ccb…386d
0x34b655…2a6f
6 touches
3 conflicts
0x152d1875…8c6f
0x34b655…2a6f
5 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x52bca89b…97d8
0x34b655…2a6f
4 touches
1 conflict
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity