pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,236,001
← previous block
next block →
recent activity
Analyzing
Block #100,236,001
10 transactions · 7 stateful · 2026-08-29 16:48:35 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,236,001
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
0x59558d29
#4
settlePredictions
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
withdraw
· blocks 1
#9
0xc6a6c2…5bb7
#8
withdraw
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51dc
0x69a5f9…2fef
4 touches
1 conflict
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0xfda39b6f…d4cc
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
0x0eac7709…66c3
0x34b655…2a6f
2 touches
0 conflicts
0x15ae3bf3…2507
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:
0x69a5f9ad…102fef
1 conflict on slot
0xaf831072f6…c551dc
Audit this contract →
← previous block
·
next block →
recent activity