pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,518,088
← previous block
next block →
recent activity
Analyzing
Block #97,518,088
9 transactions · 9 stateful · 2026-08-20 03:26:10 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,518,088
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#6
execOrders
#7
setData
#8
0x59558d29
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11e314e0…d3b2
0x34b655…2a6f
4 touches
1 conflict
0x3f4f9f22…8ad6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x73328061…40ba
0x34b655…2a6f
3 touches
1 conflict
0xe5413d91…f439
0x34b655…2a6f
3 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9285
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9289
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
0x11e314e07b…aed3b2
Audit this contract →
← previous block
·
next block →
recent activity