pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,752,626
← previous block
next block →
recent activity
Analyzing
Block #92,752,626
13 transactions · 13 stateful · 2026-08-03 10:37:18 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,752,626
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
updatePrices
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
#9
0x6a706fd6
#10
setData
#11
0x59558d29
· blocks 1
#7
execFwdPositionOps
#12
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1fd82864…6185
0x065c9d…c394
2 touches
0 conflicts
0x41cb8460…9136
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity