pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,540,973
← previous block
next block →
recent activity
Analyzing
Block #96,540,973
10 transactions · 6 stateful · 2026-08-16 16:45:58 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,540,973
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x81ab1f…8a03
#2
0xc9623387
#3
exactInputSingle
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0x13ee57fb…3a4e
0x928dc8…8207
2 touches
0 conflicts
0x586c968e…7473
0x928dc8…8207
2 touches
0 conflicts
0x59c83b42…16f4
0x928dc8…8207
2 touches
0 conflicts
0x613560f2…8d9e
0x928dc8…8207
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
0xb5f244d5d7…d9f550
Audit this contract →
← previous block
·
next block →
recent activity