pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,596,805
← previous block
next block →
recent activity
Analyzing
Block #96,596,805
11 transactions · 9 stateful · 2026-08-16 21:26:48 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.45
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,596,805
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 3
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#6
setData
#8
execOrders
#9
execOrders
#10
execOrders
#4
execFwdPositionOpsV2
· blocks 2
#5
execFwdPositionOpsV2
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x83220a94…1bd7
0x34b655…2a6f
6 touches
3 conflicts
0xcfdb765b…69b8
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x32915b25…6070
0x34b655…2a6f
4 touches
1 conflict
0x62738158…e746
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
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:
Perpl
3 conflicts on slot
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity