pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,157,765
← previous block
next block →
recent activity
Analyzing
Block #96,157,765
11 transactions · 9 stateful · 2026-08-15 08:38:19 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,157,765
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
updatePrices
#4
0x5acec890
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x16f8e14a…f6e4
0x34b655…2a6f
4 touches
1 conflict
0x8ba6e949…1344
0x34b655…2a6f
4 touches
1 conflict
0x36fd5ba2…03d7
0x34b655…2a6f
4 touches
1 conflict
0x200ed648…912f
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x6c4f8675…8f7e
0x34b655…2a6f
2 touches
0 conflicts
0x88ec0001…8715
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity