pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,783,156
← previous block
next block →
recent activity
Analyzing
Block #95,783,156
10 transactions · 6 stateful · 2026-08-14 01:13:34 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,783,156
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrder
· blocks 1
#3
execOrder
#4
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x356b3121…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x1caa030f…26bd
0x34b655…2a6f
2 touches
0 conflicts
0x1f8ecef7…5af3
0x34b655…2a6f
2 touches
0 conflicts
0x27d74e37…a5b9
0x34b655…2a6f
2 touches
0 conflicts
0x2858a318…0e14
0x34b655…2a6f
2 touches
0 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:
Perpl
1 conflict on slot
0xb256030504…6df27d
Audit this contract →
← previous block
·
next block →
recent activity