pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,556,315
← previous block
next block →
recent activity
Analyzing
Block #93,556,315
8 transactions · 7 stateful · 2026-08-06 06:00:40 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,556,315
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrders
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x6a742380
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a473699…6159
0x754704…b603
4 touches
1 conflict
0xde8a9295…0466
0x754704…b603
4 touches
1 conflict
0x1c795b3a…8e8a
0x754704…b603
4 touches
1 conflict
0x03083ef6…08aa
0x34b655…2a6f
2 touches
0 conflicts
0x12d581a6…c9e6
0x34b655…2a6f
2 touches
0 conflicts
0x18fb7bf1…a14a
0x34b655…2a6f
2 touches
0 conflicts
0x2804845a…c546
0x34b655…2a6f
2 touches
0 conflicts
0x3ad8bbeb…b084
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
0x3a4736997f…b06159
Audit this contract →
← previous block
·
next block →
recent activity