pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,164,717
← previous block
next block →
recent activity
Analyzing
Block #92,164,717
9 transactions · 8 stateful · 2026-08-01 09:19:22 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
#92,164,717
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
0x94defb17
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#5
0x94defb17
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
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x92547710…ccb7
0x7b9256…1fb2
4 touches
1 conflict
0x92547710…ccb8
0x7b9256…1fb2
4 touches
1 conflict
0x92547710…ccbb
0x7b9256…1fb2
4 touches
1 conflict
0xe01f4115…df01
0x7b9256…1fb2
4 touches
1 conflict
0xe01f4115…df02
0x7b9256…1fb2
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:
USDC (USDC)
1 conflict on slot
0x177211e248…161c2d
Audit this contract →
← previous block
·
next block →
recent activity