pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,581,040
← previous block
next block →
recent activity
Analyzing
Block #93,581,040
9 transactions · 7 stateful · 2026-08-06 08:04:58 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,581,040
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x5acec890
#4
execFwdPositionOps
· blocks 1
#6
setData
#7
exactInputSingle
#8
execOrders
#2
matchOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2b4ba7…f42d
0x754704…b603
4 touches
1 conflict
0xc07e7b41…7f0a
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x7ed8269b…cade
0x99c7a7…8bf0
4 touches
1 conflict
0x0ba2c03b…3d9f
0x754704…b603
4 touches
1 conflict
0x3fead273…ff99
0x34b655…2a6f
2 touches
0 conflicts
0x496c5f7e…80c8
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
0x9b2b4ba7eb…e3f42d
Audit this contract →
← previous block
·
next block →
recent activity