pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,457,541
← previous block
next block →
recent activity
Analyzing
Block #106,457,541
9 transactions · 8 stateful · 2026-09-20 11:59:49 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,457,541
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#4
0xab083028
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
execOrders
#3
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32070dd0…692b
0x754704…b603
4 touches
1 conflict
0x5cb99fee…00cf
0x754704…b603
4 touches
1 conflict
0xde93ff88…37ec
0x754704…b603
4 touches
1 conflict
0x19a804dc…eb94
0x99c7a7…8bf0
4 touches
1 conflict
0x58f87173…104e
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
0x32070dd0ff…ae692b
Audit this contract →
← previous block
·
next block →
recent activity