pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,283,470
← previous block
next block →
recent activity
Analyzing
Block #96,283,470
14 transactions · 11 stateful · 2026-08-15 19:10:34 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,283,470
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xf78cb219
· blocks 1
#2
0x719d975a
#4
0xab083028
#5
0x6c05cd2b
#6
0x5acec890
#7
updateDataFeedsValuesPartial
#8
0x62be7533
#9
0xcffefd2e
#10
0xcffefd2e
#11
0xcffefd2e
#12
deposit
#13
setData
#3
0xaf5e395a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0xf8d4a612…c2f8
0x065c9d…c394
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity