pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,037,625
← previous block
next block →
recent activity
Analyzing
Block #99,037,625
9 transactions · 8 stateful · 2026-08-25 11:58:58 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
#99,037,625
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
transferFrom
#4
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#6
0x57368ddf
#8
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68dfc6ca…56ac
0x34b655…2a6f
4 touches
1 conflict
0x91508d45…318b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x29201c12…99e7
0x10b5c3…6fd9
2 touches
0 conflicts
0x5bdde90e…5a31
0x10b5c3…6fd9
2 touches
0 conflicts
0x69e225ed…9335
0x10b5c3…6fd9
2 touches
0 conflicts
0x0252b4ca…99ed
0x34b655…2a6f
2 touches
0 conflicts
0x0cdc38ed…c280
0x34b655…2a6f
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
0x68dfc6ca63…a056ac
Audit this contract →
← previous block
·
next block →
recent activity