pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,753,444
← previous block
next block →
recent activity
Analyzing
Block #87,753,444
9 transactions · 7 stateful · 2026-07-14 18:26:48 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,753,444
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#4
0x0f6795d9
#5
0x3f5c179b
#8
setData
#6
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x648bb928…97f2
0x34b655…2a6f
4 touches
1 conflict
0xbeaeab89…35c6
0x34b655…2a6f
4 touches
1 conflict
0xc56d6548…50a4
0x34b655…2a6f
4 touches
1 conflict
0xceb56a75…65cc
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
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
3 conflicts on slot
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity