pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,054,978
← previous block
next block →
recent activity
Analyzing
Block #102,054,978
8 transactions · 8 stateful · 2026-09-05 01:30:24 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,054,978
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
setData
#3
updatePriceFeedsIfNecessary
#4
execFwdPositionOpsV2
· blocks 2
#6
0x6a9b70b3
#5
execFwdPositionOpsV2
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf1b853…9a33
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0cfb5d79…7ccc
0x2880ab…7b43
2 touches
0 conflicts
0x12117fd0…ec1a
0x2880ab…7b43
2 touches
0 conflicts
0x12117fd0…ec1b
0x2880ab…7b43
2 touches
0 conflicts
0x1232a81d…88d7
0x2880ab…7b43
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:
Perpl
1 conflict on slot
0xecf1b8533c…4a9a33
Audit this contract →
← previous block
·
next block →
recent activity