pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,460,853
← previous block
next block →
recent activity
Analyzing
Block #98,460,853
10 transactions · 9 stateful · 2026-08-23 10:57:52 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,460,853
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x59558d29
#3
0x5acec890
#4
execFwdPositionOpsV2
#5
0x94defb17
· blocks 1
#6
execOrders
#8
setData
#9
execute
#7
bet
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
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xeab3521a…ed00
0x8964d7…10f8
4 touches
1 conflict
0xeab3521a…ed01
0x8964d7…10f8
4 touches
1 conflict
0xeab3521a…ed04
0x8964d7…10f8
4 touches
1 conflict
0xeab3521a…ed05
0x8964d7…10f8
4 touches
1 conflict
0x442d27a8…c12f
0x34b655…2a6f
2 touches
0 conflicts
0x48f5dc69…a913
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