pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,247,543
← previous block
next block →
recent activity
Analyzing
Block #100,247,543
10 transactions · 9 stateful · 2026-08-29 17:47:18 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
#100,247,543
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
supply
· blocks 1
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#9
transfer
#4
supply
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0x00000000…0036
0x35a73b…6042
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51d6
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51dc
0x69a5f9…2fef
4 touches
1 conflict
0x168f7615…a8de
0x34b655…2a6f
2 touches
0 conflicts
0x28a2d3f3…c20e
0x34b655…2a6f
2 touches
0 conflicts
0x297de2d5…7396
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
0x2ef1d89b7e…45196d
Audit this contract →
← previous block
·
next block →
recent activity