pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,450,008
← previous block
next block →
recent activity
Analyzing
Block #86,450,008
9 transactions · 8 stateful · 2026-07-08 17:09:29 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,450,008
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#5
0xed82b078
#6
execFwdPositionOps
#7
setData
#8
0xc7e3ec2c
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x31e1ba50…3803
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0xcb9eccae…34ac
0x34b655…2a6f
4 touches
1 conflict
0xf8f3c378…789a
0x34b655…2a6f
4 touches
1 conflict
0x506cf70a…e07a
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
3 conflicts on slot
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity