pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,317,559
← previous block
next block →
recent activity
Analyzing
Block #99,317,559
11 transactions · 10 stateful · 2026-08-26 11:31:04 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,317,559
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0x6ad2e98b
· blocks 1
#4
0x6dc24a…ab72
#6
0x94defb17
· blocks 1
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#10
setData
#5
0x3f5c179b
#9
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w0
9
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
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186a
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186e
0x2b46c0…1669
2 touches
0 conflicts
0xcfe06a18…b5b5
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