pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,556,333
← previous block
next block →
recent activity
Analyzing
Block #93,556,333
10 transactions · 10 stateful · 2026-08-06 06:00:46 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,556,333
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x222d4ad6
#6
placeAndExecuteMarketSell
#8
0x6a742385
#9
setData
#2
matchOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9feedc78…da4a
0x754704…b603
4 touches
1 conflict
0xfe4e584c…50ff
0x754704…b603
4 touches
1 conflict
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
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:
Perpl
1 conflict on slot
0xe4af4c87c3…c59964
Audit this contract →
← previous block
·
next block →
recent activity