pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,405,050
← previous block
next block →
recent activity
Analyzing
Block #95,405,050
9 transactions · 8 stateful · 2026-08-12 17:30:12 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,405,050
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
0x3f5c179b
#4
execFwdPositionOps
· blocks 1
#6
0x6a7cae1c
#7
setData
#8
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe77c721b…7588
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2b0a93aa…499f
0x34b655…2a6f
4 touches
1 conflict
0x5b6cd435…c922
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0xac16b836…d418
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x80884f59…ac94
0x34b655…2a6f
3 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
0xe77c721bb9…5c7588
Audit this contract →
← previous block
·
next block →
recent activity