pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,983,366
← previous block
next block →
recent activity
Analyzing
Block #98,983,366
16 transactions · 13 stateful · 2026-08-25 07:22:57 UTC
Parallelism
88
/100
Blocked
8
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,983,366
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0xab083028
#3
0x6ad2e98b
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
execOrders
#7
execOrders
#8
0x59558d29
#9
execPerpOps
#10
execPerpOps
#11
execFwdPositionOpsV2
#12
0x3f5c179b
#13
transfer
· blocks 1
#15
setData
#14
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
13
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00b6b37f…a0d8
0x34b655…2a6f
2 touches
0 conflicts
0x0a300d4d…a515
0x34b655…2a6f
2 touches
0 conflicts
0x1976ecad…1f83
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x36918c55…8424
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
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity