pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,501,338
← previous block
next block →
recent activity
Analyzing
Block #93,501,338
12 transactions · 12 stateful · 2026-08-06 01:24:19 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,501,338
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
0xa96df62f
#5
0xa96df62f
#6
poke
#7
updateDataFeedsValuesPartial
#8
placeAndExecuteMarketSell
#9
setData
#10
execOrders
#11
0x59558d29
#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
0x9b2b4ba7…f42d
0x754704…b603
4 touches
1 conflict
0x3051f72d…943e
0x99c7a7…8bf0
4 touches
1 conflict
0x7ed8269b…cade
0x99c7a7…8bf0
4 touches
1 conflict
0xc07e7b41…7f0a
0x754704…b603
4 touches
1 conflict
0x0ba2c03b…3d9f
0x754704…b603
4 touches
1 conflict
0x3352fed8…8092
0x01bff4…1071
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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