pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,713,170
← previous block
next block →
recent activity
Analyzing
Block #108,713,170
13 transactions · 10 stateful · 2026-09-28 09:17:00 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,713,170
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x5acec890
#3
0x5acec890
#4
execFwdPositionOpsV2
#5
handleOp
#6
0x3f5c179b
· blocks 1
#8
execFwdPositionOpsV2
#9
0xb2c758…4fd0
#10
setData
#11
withdraw
#12
execOrders
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c40f150…e5d6
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3e49348b…9445
0x34b655…2a6f
2 touches
0 conflicts
0x45885570…ed97
0x34b655…2a6f
2 touches
0 conflicts
0x47679846…4d1b
0x34b655…2a6f
2 touches
0 conflicts
0x5f251b96…6054
0x34b655…2a6f
2 touches
0 conflicts
0x815d5e8a…058c
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x2c40f1505b…e8e5d6
Audit this contract →
← previous block
·
next block →
recent activity