pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,551,042
← previous block
next block →
recent activity
Analyzing
Block #95,551,042
12 transactions · 10 stateful · 2026-08-13 05:45:04 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,551,042
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5acec890
· blocks 1
#6
0x0c7abd22
#7
execFwdPositionOps
#8
relay
#9
0x6a7d5a58
#10
setData
#11
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
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07b5dc27…d54c
0x34b655…2a6f
2 touches
0 conflicts
0x0b87c899…c0f9
0x34b655…2a6f
2 touches
0 conflicts
0x2328941c…84d3
0x34b655…2a6f
2 touches
0 conflicts
0x2da28f3b…cc6e
0x34b655…2a6f
2 touches
0 conflicts
0x3cbfa5aa…cc9b
0x34b655…2a6f
2 touches
0 conflicts
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
0x2840c278a3…01bbc7
Audit this contract →
← previous block
·
next block →
recent activity