pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,772,310
← previous block
next block →
recent activity
Analyzing
Block #92,772,310
10 transactions · 8 stateful · 2026-08-03 12:16:21 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,772,310
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 2
#6
0x0f6795d9
#9
setData
#7
0x0f6795d9
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4c059d8…185d
0x34b655…2a6f
4 touches
1 conflict
0xf3aa4aa5…2cee
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0cdc38ed…c280
0x34b655…2a6f
2 touches
0 conflicts
0x24a21f33…0681
0x34b655…2a6f
2 touches
0 conflicts
0x3cbf66d3…90fc
0x754704…b603
2 touches
0 conflicts
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
0xc4c059d8f6…bf185d
Audit this contract →
← previous block
·
next block →
recent activity