pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,027,938
← previous block
next block →
recent activity
Analyzing
Block #106,027,938
8 transactions · 8 stateful · 2026-09-18 23:57:40 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,027,938
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
setData
#6
execFwdPositionOpsV2
#7
execOrders
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4c946a4…b8d4
0x754704…b603
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
4 touches
1 conflict
0x4b7ae908…3c95
0x99c7a7…8bf0
4 touches
1 conflict
0xdd084cf8…1a71
0x99c7a7…8bf0
4 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0x2b773226…dc34
0x34b655…2a6f
2 touches
0 conflicts
0x3055bb94…0598
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
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:
USDC (USDC)
1 conflict on slot
0xd4c946a466…37b8d4
Audit this contract →
← previous block
·
next block →
recent activity