pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,737,559
← previous block
next block →
recent activity
Analyzing
Block #95,737,559
8 transactions · 7 stateful · 2026-08-13 21:24:15 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,737,559
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#5
0x94defb17
· blocks 1
#7
setData
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01d796b1…42af
0x968279…9342
4 touches
1 conflict
0x01d796b1…42b0
0x968279…9342
4 touches
1 conflict
0x01d796b1…42b2
0x968279…9342
4 touches
1 conflict
0x3fa7538b…5fd9
0x968279…9342
4 touches
1 conflict
0x3fa7538b…5fda
0x968279…9342
4 touches
1 conflict
0x3fa7538b…5fdc
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
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:
0x96827978…f09342
1 conflict on slot
0x01d796b1ad…fd42af
Audit this contract →
← previous block
·
next block →
recent activity