pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,453,454
← previous block
next block →
recent activity
Analyzing
Block #99,453,454
35 transactions · 25 stateful · 2026-08-26 22:55:22 UTC
Parallelism
86
/100
Blocked
48
%
Avg conflicts / tx
0.74
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,453,454
· 35 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x4a39de…bd7c
#2
____MEV_X____Ga543
#3
execute
· blocks 4
#5
0xcf7468f4
#6
0xab083028
· blocks 1
#7
0x6af46a…2ecd
#8
0x5acec890
· blocks 4
#9
execute
#10
0x0c7abd22
· blocks 2
#11
0x6ad2e98b
#13
updateDataFeedsValuesPartial
#17
0x4cb2db39
#18
0x59558d29
#19
0xb414539a
#20
0xe3a3c9cc
#24
execFwdPositionOpsV2
#25
execFwdPositionOpsV2
#26
setData
#27
0x3f5c179b
· blocks 1
#29
0x0c7abd22
#30
redeemDelegations
#34
execute
#4
0xa9b28aa6
· blocks 4
#12
0x32d01e04
· blocks 1
#15
0x5acec890
· blocks 2
#14
0x0c7abd22
· blocks 3
#16
0x928e4afa
· blocks 1
#21
0xa9b28aa6
· blocks 1
#22
execFwdPositionOpsV2
· blocks 1
#23
0x62be7533
· blocks 1
#28
0x0c7abd22
#31
0xed82b078
#32
execOrders
#33
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
8
w0
10
w0
12
w1
14
w2
15
w1
16
w2
21
w2
22
w3
23
w3
28
w3
31
w3
32
w4
33
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc18ede0f…d5bc
0xd32edf…ff58
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0d63ff4f…4f9a
0x34b655…2a6f
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:
Uniswap: PoolManager
10 conflicts on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity