pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,277,446
← previous block
next block →
recent activity
Analyzing
Block #94,277,446
9 transactions · 7 stateful · 2026-08-08 18:33:42 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,277,446
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#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
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x8784a7c7…786e
0x34b655…2a6f
4 touches
1 conflict
0xe3badf57…0e9b
0x34b655…2a6f
4 touches
1 conflict
0xe9a321bc…88d5
0x34b655…2a6f
4 touches
1 conflict
0xeb9b6ffc…3aab
0x34b655…2a6f
4 touches
1 conflict
0xeb9b6ffc…3aac
0x34b655…2a6f
4 touches
1 conflict
0x07ec3a47…8ec9
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity