pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,217,585
← previous block
next block →
recent activity
Analyzing
Block #98,217,585
9 transactions · 9 stateful · 2026-08-22 14:33:42 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,217,585
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
matchOrders
· blocks 1
#4
execOrders
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
setData
#3
matchOrders
#8
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba68e65e…c29a
0x754704…b603
4 touches
1 conflict
0x3129b531…9db1
0x754704…b603
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0x17b301d6…9bb9
0x8f415d…5241
3 touches
1 conflict
0x329f2f7d…dcff
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
0xba68e65e01…39c29a
Audit this contract →
← previous block
·
next block →
recent activity