pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,558,338
← previous block
next block →
recent activity
Analyzing
Block #97,558,338
11 transactions · 11 stateful · 2026-08-20 06:49:30 UTC
Parallelism
82
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,558,338
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x8263f5d9
#3
execOrders
· blocks 1
#4
0x3f5c179b
#5
0x94defb17
· blocks 1
#7
0xed82b078
#9
setData
#6
bet
#8
execFwdPositionOpsV2
#10
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w0
6
w1
8
w1
10
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
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xcc02d79e…7e86
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9289
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0xce1efe70…2ec8
0x2b46c0…1669
2 touches
0 conflicts
0xf17982ba…359a
0x2b46c0…1669
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