pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,257,639
← previous block
next block →
recent activity
Analyzing
Block #87,257,639
9 transactions · 8 stateful · 2026-07-12 11:10:12 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,257,639
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#6
0x0f6795d9
#7
0x6a53768c
#8
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbeb25a4…725a
0x34b655…2a6f
4 touches
1 conflict
0x055b6077…0815
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe741c135…25a9
0x34b655…2a6f
4 touches
1 conflict
0xe9ac193d…f728
0x34b655…2a6f
4 touches
1 conflict
0xe9ac193d…f729
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
1 conflict on slot
0xfbeb25a44e…b8725a
Audit this contract →
← previous block
·
next block →
recent activity