pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,977,133
← previous block
next block →
recent activity
Analyzing
Block #95,977,133
11 transactions · 10 stateful · 2026-08-14 17:29:35 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,977,133
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execFwdPositionOpsV2
#3
updateDataFeedsValuesPartial
#4
0x94defb17
· blocks 1
#6
execFwdPositionOpsV2
#7
setData
#8
0x61d59c2d
#9
execOrders
· blocks 1
#5
0x94defb17
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe0464d0…00ce
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x30d023a4…72a6
0x968279…9342
4 touches
1 conflict
0x30d023a4…72a7
0x968279…9342
4 touches
1 conflict
0x30d023a4…72aa
0x968279…9342
4 touches
1 conflict
0x30d023a4…72ab
0x968279…9342
4 touches
1 conflict
0x30d023a4…72ad
0x968279…9342
4 touches
1 conflict
0xbe0464d0…00cb
0x968279…9342
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
0xbe0464d0b3…ec00ce
Audit this contract →
← previous block
·
next block →
recent activity