pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,154,356
← previous block
next block →
recent activity
Analyzing
Block #95,154,356
11 transactions · 11 stateful · 2026-08-11 20:16:14 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,154,356
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
0x94defb17
· blocks 1
#8
execFwdPositionOps
#9
setData
#10
execOrders
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1706096a…b882
0x968279…9342
4 touches
1 conflict
0x1706096a…b884
0x968279…9342
4 touches
1 conflict
0x39879f6a…85db
0x968279…9342
4 touches
1 conflict
0x39879f6a…85dc
0x968279…9342
4 touches
1 conflict
0x39879f6a…85df
0x968279…9342
4 touches
1 conflict
0x39879f6a…85e0
0x968279…9342
4 touches
1 conflict
0x39879f6a…85e2
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
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
0x1706096a44…29b882
Audit this contract →
← previous block
·
next block →
recent activity