pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,568,640
← previous block
next block →
recent activity
Analyzing
Block #95,568,640
9 transactions · 8 stateful · 2026-08-13 07:13:34 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,568,640
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
#5
0x94defb17
· blocks 1
#7
execFwdPositionOps
#8
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
0x7bbd3079…7c94
0x968279…9342
4 touches
1 conflict
0x7bbd3079…7c96
0x968279…9342
4 touches
1 conflict
0xdcba8386…5a84
0x968279…9342
4 touches
1 conflict
0xdcba8386…5a85
0x968279…9342
4 touches
1 conflict
0xdcba8386…5a88
0x968279…9342
4 touches
1 conflict
0xdcba8386…5a89
0x968279…9342
4 touches
1 conflict
0xdcba8386…5a8a
0x968279…9342
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
0x7bbd307925…f77c94
Audit this contract →
← previous block
·
next block →
recent activity