pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,105,427
← previous block
next block →
recent activity
Analyzing
Block #99,105,427
13 transactions · 13 stateful · 2026-08-25 17:43:41 UTC
Parallelism
85
/100
Blocked
23
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,105,427
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#6
setData
#7
updatePosition
#8
batchUpdate
#9
execFwdPositionOpsV2
#10
0x6a8dd4c5
#11
execOrders
· blocks 1
#2
0xab083028
#5
0x62be7533
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xe697367a…12a0
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb5ed555a…386f
0x3bd359…433a
2 touches
0 conflicts
0xef647ac1…26c5
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity