pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,028,333
← previous block
next block →
recent activity
Analyzing
Block #106,028,333
9 transactions · 9 stateful · 2026-09-18 23:59:39 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,028,333
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
setData
#7
execFwdPositionOpsV2
#8
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
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0xadd06891…6aee
0x99c7a7…8bf0
4 touches
1 conflict
0x643fa4aa…a822
0x754704…b603
4 touches
1 conflict
0xd1eae902…bfd4
0x754704…b603
4 touches
1 conflict
0x15ff2ef2…1cc4
0x8f415d…5241
3 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
2 touches
0 conflicts
0x70a53d84…2d91
0x754704…b603
2 touches
0 conflicts
0xc98b6062…73eb
0x754704…b603
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
0x73bb65fcbe…87650d
Audit this contract →
← previous block
·
next block →
recent activity