pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,001,737
← previous block
next block →
recent activity
Analyzing
Block #92,001,737
11 transactions · 9 stateful · 2026-07-31 19:39:40 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,001,737
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
updateTemporalNumericValuesV1
#6
execOrders
#7
execOrders
#8
execOrders
#9
setData
#10
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
0x0e854949…baa7
0x754704…b603
4 touches
1 conflict
0x29ba534c…fe06
0x754704…b603
4 touches
1 conflict
0x303ace4f…eae8
0x754704…b603
4 touches
1 conflict
0x3355228b…a9fe
0x34b655…2a6f
2 touches
0 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
2 touches
0 conflicts
0x72491751…1519
0x34b655…2a6f
2 touches
0 conflicts
0x7ef4ba09…2a25
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
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
0x0e85494967…b0baa7
Audit this contract →
← previous block
·
next block →
recent activity