pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,452,018
← previous block
next block →
recent activity
Analyzing
Block #92,452,018
9 transactions · 9 stateful · 2026-08-02 09:24:12 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,452,018
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
updatePriceFeedsIfNecessary
#5
execOrders
#6
setData
#7
0x59558d29
· blocks 1
#2
execFwdPositionOps
· blocks 1
#8
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x33b9b421…f42c
0x34b655…2a6f
6 touches
3 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
6 touches
3 conflicts
0x3d49013e…1338
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d9bea1c…2ca1
0x34b655…2a6f
4 touches
1 conflict
0x809f2ba8…89d3
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
0x69ee34d107…a730f8
Audit this contract →
← previous block
·
next block →
recent activity