pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,059,079
← previous block
next block →
recent activity
Analyzing
Block #92,059,079
16 transactions · 14 stateful · 2026-08-01 00:28:03 UTC
Parallelism
81
/100
Blocked
14
%
Avg conflicts / tx
0.19
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,059,079
· 16 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5acec890
#4
0x5acec890
#5
transfer
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execOrders
#10
transfer
· blocks 2
#13
0xe9316489
#14
setData
#15
0x59558d29
#11
transfer
· blocks 1
#12
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x076ca8d0…8fa0
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
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:
USDC (USDC)
3 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity