pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,674,445
← previous block
next block →
recent activity
Analyzing
Block #98,674,445
12 transactions · 11 stateful · 2026-08-24 05:24:26 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,674,445
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
batchUpdate
#8
0x94defb17
· blocks 1
#10
setData
#11
execOrders
#9
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xf3bc57c6…b376
0x8964d7…10f8
4 touches
1 conflict
0xf3bc57c6…b377
0x8964d7…10f8
4 touches
1 conflict
0xf3bc57c6…b37a
0x8964d7…10f8
4 touches
1 conflict
0xf3bc57c6…b37b
0x8964d7…10f8
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
2 touches
0 conflicts
0xc4b42bc6…8008
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
0x2a07e64ef2…a8fe77
Audit this contract →
← previous block
·
next block →
recent activity