pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,837,888
← previous block
next block →
recent activity
Analyzing
Block #96,837,888
9 transactions · 7 stateful · 2026-08-17 17:39:21 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,837,888
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
0x5acec890
#4
updatePrices
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x2cb195…bd18
#2
0x5acec890
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x24e578ef…2049
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x07969058…0fef
0x34b655…2a6f
2 touches
0 conflicts
0x1dafc5cd…f56f
0x34b655…2a6f
2 touches
0 conflicts
0x306233f2…96c3
0x34b655…2a6f
2 touches
0 conflicts
0x3661f59a…874a
0x34b655…2a6f
2 touches
0 conflicts
0x4188cc5f…2d2e
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity