pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,440,244
← previous block
next block →
recent activity
Analyzing
Block #93,440,244
12 transactions · 12 stateful · 2026-08-05 20:17:11 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,440,244
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#4
0x6ad2e98b
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOps
#9
setData
#10
execOrders
#11
0x59558d29
#3
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bef2c97…ba12
0x754704…b603
4 touches
1 conflict
0x9feedc78…da4a
0x754704…b603
4 touches
1 conflict
0xfe4e584c…50ff
0x754704…b603
4 touches
1 conflict
0x768e0634…d2f2
0x99c7a7…8bf0
4 touches
1 conflict
0xf4dd9166…ba9d
0x99c7a7…8bf0
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xdf7d5f47…075a
0x065c9d…c394
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
0x6bef2c9706…bbba12
Audit this contract →
← previous block
·
next block →
recent activity