pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,064,682
← previous block
next block →
recent activity
Analyzing
Block #102,064,682
12 transactions · 11 stateful · 2026-09-05 02:19:34 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
#102,064,682
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#9
forceDeallocate
· blocks 1
#11
execOrders
#10
forceDeallocate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89e87a02…9953
0x754704…b603
4 touches
1 conflict
0x9a669e4f…70a0
0x754704…b603
4 touches
1 conflict
0x3cf9b957…a859
0x80017b…bb59
4 touches
1 conflict
0x71db4594…0e0c
0x754704…b603
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
0x89e87a028e…0b9953
Audit this contract →
← previous block
·
next block →
recent activity