pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,295,581
← previous block
next block →
recent activity
Analyzing
Block #95,295,581
11 transactions · 10 stateful · 2026-08-12 08:15:43 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,295,581
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute302
· blocks 2
#4
updatePrices
#5
0x000000b2
#6
updateDataFeedsValuesPartial
#7
0x94defb17
#8
execFwdPositionOps
#9
setData
#10
execOrders
#2
execute302
· blocks 1
#3
execute302
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x446f2734…8b54
0x0a3323…0a3c
6 touches
3 conflicts
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0x0b1d86ea…d766
0x34b655…2a6f
2 touches
0 conflicts
0xff3addfc…633e
0x6f4756…dd5b
2 touches
0 conflicts
0x177211e2…1c2d
0x754704…b603
2 touches
0 conflicts
0x521a5982…a82a
0x754704…b603
2 touches
0 conflicts
0x00000000…0006
0x968279…9342
2 touches
0 conflicts
0x0aca6dd6…240a
0x968279…9342
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:
0x0a332311…6e0a3c
3 conflicts on slot
0x446f273453…878b54
Audit this contract →
← previous block
·
next block →
recent activity