pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,108,350
← previous block
next block →
recent activity
Analyzing
Block #100,108,350
16 transactions · 11 stateful · 2026-08-29 06:05:49 UTC
Parallelism
88
/100
Blocked
9
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,108,350
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
createModule
#3
exactInputSingle
#4
execute
#5
matchOrders
#6
updatePrices
#7
0xab083028
#8
0x5acec890
· blocks 1
#9
0xe3a3c9cc
#10
setData
#11
0x62be7533
#12
batchUpdate
#13
0x57368ddf
#15
execOrders
#14
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x8e44ce6a…fe19
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf6c1a79…b07f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x2c41b6b9…edff
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:
Perpl
1 conflict on slot
0x31d88d27c1…837617
Audit this contract →
← previous block
·
next block →
recent activity