pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,408,760
← previous block
next block →
recent activity
Analyzing
Block #106,408,760
8 transactions · 7 stateful · 2026-09-20 07:54:15 UTC
Parallelism
63
/100
Blocked
43
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,408,760
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#2
setData
#4
0x1ea3e879
· blocks 2
#7
execFwdPositionOpsV2
#3
0x3f5c179b
#5
0x1ea3e879
· blocks 1
#6
0x1ea3e879
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0034dce9…b41f
0x6f6493…b480
6 touches
3 conflicts
0x01ccd702…6edb
0x6f6493…b480
6 touches
3 conflicts
0x0575feaa…792a
0x6f6493…b480
6 touches
3 conflicts
0x07ac73dc…ea96
0x6f6493…b480
6 touches
3 conflicts
0x0bdb66db…4149
0x6f6493…b480
6 touches
3 conflicts
0x121965c2…4916
0x6f6493…b480
6 touches
3 conflicts
0x15d6222d…f4f9
0x6f6493…b480
6 touches
3 conflicts
0x195ab1e0…433f
0x6f6493…b480
6 touches
3 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:
0x6f6493e3…08b480
3 conflicts on slot
0x0034dce9ea…f7b41f
Audit this contract →
← previous block
·
next block →
recent activity