pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,805,609
← previous block
next block →
recent activity
Analyzing
Block #107,805,609
10 transactions · 10 stateful · 2026-09-25 05:08:27 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,805,609
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x5acec890
#4
0x84403c1b
· blocks 1
#6
execFwdPositionOpsV2
#7
0x6ab601cd
#8
setData
#9
0x0c7abd22
#5
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x441d5d98…59ef
0x34b655…2a6f
4 touches
1 conflict
0x87b3c188…6ea2
0x34b655…2a6f
4 touches
1 conflict
0xe3254525…23a6
0x34b655…2a6f
4 touches
1 conflict
0x0d826721…a4bf
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9284
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9285
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9287
0x34ae4d…3fc5
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
0x441d5d982b…c159ef
Audit this contract →
← previous block
·
next block →
recent activity