pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,734,112
← previous block
next block →
recent activity
Analyzing
Block #97,734,112
10 transactions · 9 stateful · 2026-08-20 21:45:48 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,734,112
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
execOrders
#8
modifyLiquidities
#7
execOrders
#9
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x10f0a1bf…12c3
0x34b655…2a6f
2 touches
0 conflicts
0x1109ec90…ba98
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6213
0x34b655…2a6f
2 touches
0 conflicts
0x1e10796e…6214
0x34b655…2a6f
2 touches
0 conflicts
0x1fa90d39…35c6
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
0x326a02b5c5…5c8dad
Audit this contract →
← previous block
·
next block →
recent activity