pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,922,283
← previous block
next block →
recent activity
Analyzing
Block #93,922,283
11 transactions · 10 stateful · 2026-08-07 12:40:57 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,922,283
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#3
0xab083028
· blocks 1
#4
execFwdPositionOps
#5
0x3f5c179b
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#2
executePacked
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0d3faac…ae01
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x405da62e…192a
0xa6afd3…d132
4 touches
1 conflict
0xb476ee35…c627
0xa6afd3…d132
4 touches
1 conflict
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0006
0x158106…0e58
2 touches
0 conflicts
0x00000000…0000
0x2d82ac…5fd8
2 touches
0 conflicts
0x00000000…0001
0x2d82ac…5fd8
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)
1 conflict on slot
0xa0d3faaca4…ecae01
Audit this contract →
← previous block
·
next block →
recent activity