pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,468,675
← previous block
next block →
recent activity
Analyzing
Block #83,468,675
10 transactions · 9 stateful · 2026-06-24 21:50:03 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,468,675
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#4
forward
#5
setData
#6
0xe9316489
#8
execOrders
#9
0xc7e3ec2c
#3
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89fa3104…8020
0x34b655…2a6f
6 touches
3 conflicts
0xc7743c5f…108e
0x34b655…2a6f
4 touches
1 conflict
0x24afc70d…36ef
0x34b655…2a6f
4 touches
1 conflict
0x0430f721…b772
0x34b655…2a6f
2 touches
0 conflicts
0x0720d2a9…57f6
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0a02029e…5198
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
3 conflicts on slot
0x89fa310462…5f8020
Audit this contract →
← previous block
·
next block →
recent activity