pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,013,450
← previous block
next block →
recent activity
Analyzing
Block #92,013,450
11 transactions · 10 stateful · 2026-07-31 20:38:33 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,013,450
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
execFwdPositionOps
· blocks 1
#6
execOrders
#7
0x6a6d0841
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465bae8…d3ac
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x1e2721…7805
2 touches
0 conflicts
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x17530abf…5f20
0x754704…b603
2 touches
0 conflicts
0x431fa96d…6ac0
0x754704…b603
2 touches
0 conflicts
0x6bef2c97…ba12
0x754704…b603
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
0x9465bae81f…abd3ac
Audit this contract →
← previous block
·
next block →
recent activity