pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,998,947
← previous block
next block →
recent activity
Analyzing
Block #91,998,947
9 transactions · 9 stateful · 2026-07-31 19:25:38 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,998,947
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#2
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a6cf72a
#7
setData
#8
0x59558d29
#3
execFwdPositionOps
#4
mergePositions
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07010ea7…c45a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1af53e83…c72e
0x754704…b603
4 touches
1 conflict
0xd930d57a…3bfb
0x99c7a7…8bf0
4 touches
1 conflict
0x1e302fd3…642c
0x34b655…2a6f
2 touches
0 conflicts
0x1eb410fd…591d
0x34b655…2a6f
2 touches
0 conflicts
0x22437dc7…0b63
0x34b655…2a6f
2 touches
0 conflicts
0x4118bd12…924a
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
0x07010ea7a3…72c45a
Audit this contract →
← previous block
·
next block →
recent activity