pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,572,381
← previous block
next block →
recent activity
Analyzing
Block #98,572,381
11 transactions · 11 stateful · 2026-08-23 20:32:57 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,572,381
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0xa96df62f
#4
0x59558d29
#5
executeBatch
#6
0x94defb17
· blocks 1
#8
execFwdPositionOpsV2
#9
0x6a8b5971
#10
setData
#7
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18ca1518…b69a
0x34b655…2a6f
2 touches
0 conflicts
0x272e5bd6…252d
0x34b655…2a6f
2 touches
0 conflicts
0x27b6010e…e4aa
0x34b655…2a6f
2 touches
0 conflicts
0x44c9cb1f…59b3
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