pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,564,415
← previous block
next block →
recent activity
Analyzing
Block #93,564,415
12 transactions · 11 stateful · 2026-08-06 06:41:23 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,564,415
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execPerpOps
#4
execPerpOps
#5
0x5acec890
· blocks 1
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a742d0b
#10
transfer
#11
setData
#2
matchOrders
#6
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50be7f5d…2a30
0x754704…b603
4 touches
1 conflict
0xcbcfed5b…96a6
0x754704…b603
4 touches
1 conflict
0xfe4e584c…50ff
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1b744ff7…3354
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x3dcbc94a…a380
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
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
0x50be7f5dbf…bf2a30
Audit this contract →
← previous block
·
next block →
recent activity