pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,195,353
← previous block
next block →
recent activity
Analyzing
Block #85,195,353
10 transactions · 9 stateful · 2026-07-02 21:43:32 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,195,353
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x6f0a5635
· blocks 1
#4
0x5a5d9a99
#6
0x6a46dbfc
#7
setData
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#5
createModule
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x97a0cd85…cfca
0x080ec9…fe74
2 touches
0 conflicts
0xa0bab64e…b8c0
0x080ec9…fe74
2 touches
0 conflicts
0x00000000…0008
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…0009
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…000a
0x14c8e4…fdcb
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:
Uniswap: PoolManager
1 conflict on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity