pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,006,953
← previous block
next block →
recent activity
Analyzing
Block #92,006,953
11 transactions · 10 stateful · 2026-07-31 20:05:53 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,006,953
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
#5
0x94defb17
· blocks 1
#7
0xed82b078
#8
0xed82b078
#9
setData
#10
0x59558d29
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb85de79…3e7d
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0xd121bc24…efd8
0x7b9256…1fb2
4 touches
1 conflict
0xd121bc24…efd9
0x7b9256…1fb2
4 touches
1 conflict
0xd121bc24…efdc
0x7b9256…1fb2
4 touches
1 conflict
0xeb85de79…3e7c
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:
0x7b9256fd…e21fb2
1 conflict on slot
0xeb85de7903…253e7d
Audit this contract →
← previous block
·
next block →
recent activity