pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,567,822
← previous block
next block →
recent activity
Analyzing
Block #96,567,822
9 transactions · 8 stateful · 2026-08-16 19:01:01 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,567,822
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postStateList
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#6
0x57368ddf
#7
transfer
#8
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe429135d…613c
0x34b655…2a6f
4 touches
1 conflict
0xe429135d…613d
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0x394971b4…63d9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x93dda39a…de4d
0x34b655…2a6f
4 touches
1 conflict
0xb2b474b7…c657
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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity