pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,916,103
← previous block
next block →
recent activity
Analyzing
Block #95,916,103
20 transactions · 13 stateful · 2026-08-14 12:22:33 UTC
Parallelism
90
/100
Blocked
31
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,916,103
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa9b28aa6
· blocks 1
#2
0x50a0b275
#3
executePacked
#4
0x008a140d
#5
0x719d975a
#6
0x0c7abd22
· blocks 1
#8
0xab083028
· blocks 1
#11
0xb414539a
#12
updatePrices
#13
execOrders
#14
updateDataFeedsValuesPartial
#15
execFwdPositionOpsV2
#16
0x62be7533
#17
execFwdPositionOpsV2
· blocks 1
#19
setData
#7
0xf8b1083e
#9
0xab083028
#10
0x0c7abd22
#18
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
7
w1
8
w0
9
w1
10
w1
17
w0
18
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0000
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0001
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
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:
USDC (USDC)
1 conflict on slot
0xa060b59478…f7669d
Audit this contract →
← previous block
·
next block →
recent activity