pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,000,481
← previous block
next block →
recent activity
Analyzing
Block #92,000,481
17 transactions · 17 stateful · 2026-07-31 19:33:21 UTC
Parallelism
88
/100
Blocked
6
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,000,481
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x94defb17
· blocks 1
#6
execFwdPositionOps
#8
0x6a6cf8f8
#9
setData
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
0x59558d29
#7
withdrawReserve
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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
0xe1f61186c5…67e2f8
Audit this contract →
← previous block
·
next block →
recent activity