pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,320,456
← previous block
next block →
recent activity
Analyzing
Block #99,320,456
10 transactions · 10 stateful · 2026-08-26 11:45:38 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,320,456
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x5acec890
#4
setData
#5
execFwdPositionOpsV2
#6
batchUpdate
#7
claim
· blocks 1
#9
execOrders
#8
0xc925b3a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xffc7cd67…5e7c
0x8964d7…10f8
4 touches
1 conflict
0xffc7cd67…5e7d
0x8964d7…10f8
3 touches
1 conflict
0x091a7571…38d8
0x2b46c0…1669
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9285
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9286
0x2b46c0…1669
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
0x2a07e64ef2…a8fe77
Audit this contract →
← previous block
·
next block →
recent activity