← previous blocknext block →recent activity
Analyzing
Block #87,757,774
18 transactions · 16 stateful · 2026-07-14 18:55:44 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,757,774 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w110w211w313w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfb7adca…51d7
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x5b297b4d…b05f
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x33da0dfa…bac6
0x34b655…2a6f
4 touches
1 conflict
0x3b80f5b2…72ad
0x34b655…2a6f
4 touches
1 conflict
0x50ff67ff…7fb8
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
6 conflicts on slot 0xbfb7adcac2…1751d7
Audit this contract →
← previous block·next block →recent activity