pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,171,440
← previous block
next block →
recent activity
Analyzing
Block #85,171,440
10 transactions · 9 stateful · 2026-07-02 19:04:11 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,171,440
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
execOrders
#3
execPerpOps
· blocks 1
#5
relay
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#2
compound
#4
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x1ca5aec6…c1e1
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x24227bc5…cb16
0x34b655…2a6f
2 touches
0 conflicts
0x322a91cf…edb6
0x34b655…2a6f
2 touches
0 conflicts
0x359fc107…551d
0x34b655…2a6f
2 touches
0 conflicts
0x3891cd1c…e740
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:
Monad: Staking
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity