pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,722,779
← previous block
next block →
recent activity
Analyzing
Block #95,722,779
9 transactions · 8 stateful · 2026-08-13 20:09:55 UTC
Parallelism
56
/100
Blocked
50
%
Avg conflicts / tx
0.78
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,722,779
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
matchOrders
#2
0xab083028
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x94defb17
· blocks 3
#3
0xab083028
#6
0x94defb17
· blocks 2
#7
0x94defb17
· blocks 1
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3accfd83…8170
0x968279…9342
8 touches
6 conflicts
0x3accfd83…8173
0x968279…9342
8 touches
6 conflicts
0xca98024c…20a5
0x968279…9342
8 touches
6 conflicts
0xca98024c…20a6
0x968279…9342
8 touches
6 conflicts
0xca98024c…20a8
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0x3accfd83…8171
0x968279…9342
8 touches
6 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:
0x96827978…f09342
6 conflicts on slot
0x3accfd8333…d88170
Audit this contract →
← previous block
·
next block →
recent activity