pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,424,433
← previous block
next block →
recent activity
Analyzing
Block #98,424,433
12 transactions · 12 stateful · 2026-08-23 07:54:22 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,424,433
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
0x59558d29
#4
execFwdPositionOpsV2
#5
claim
· blocks 1
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
0x6a8aa7a6
#10
setData
#11
execOrders
#6
0xc925b3a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
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
0xd64458c3…17b3
0x8964d7…10f8
4 touches
1 conflict
0xd64458c3…17b4
0x8964d7…10f8
3 touches
1 conflict
0x63726607…4e47
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x81d11f44…69b8
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
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