pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,801,005
← previous block
next block →
recent activity
Analyzing
Block #106,801,005
11 transactions · 10 stateful · 2026-09-21 16:49:27 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,801,005
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#2
execOrder
#3
0x5acec890
#4
0x5acec890
#7
execOrders
#8
setData
#9
0x0c7abd22
#10
execOrders
#5
execOrders
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x7f0725e9…66f7
0x34b655…2a6f
5 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x6b7dd8ae…86cc
0x34b655…2a6f
4 touches
1 conflict
0x0372d150…8a4d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf1feb16a…a1d3
0x34b655…2a6f
3 touches
1 conflict
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
3 conflicts on slot
0x1b25f26097…52c429
Audit this contract →
← previous block
·
next block →
recent activity