pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,012,245
← previous block
next block →
recent activity
Analyzing
Block #102,012,245
9 transactions · 8 stateful · 2026-09-04 21:54:05 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,012,245
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0xab083028
#4
executeBatch
#5
collect
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
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
0xd008c6e3…ecd2
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x4260a8c3…bb77
0x34b655…2a6f
4 touches
1 conflict
0x62bb20db…431e
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0xa6afd3…d132
2 touches
0 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
2 touches
0 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
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:
Perpl
1 conflict on slot
0xd008c6e313…63ecd2
Audit this contract →
← previous block
·
next block →
recent activity