pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,956,744
← previous block
next block →
recent activity
Analyzing
Block #101,956,744
11 transactions · 9 stateful · 2026-09-04 17:12:34 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,956,744
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xdb834625
#3
0x5acec890
· blocks 3
#5
0x59558d29
#6
redeemDelegations
#7
setData
#10
transfer
#4
0x5acec890
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
4 touches
1 conflict
0xb4131ba5…6924
0x34b655…2a6f
4 touches
1 conflict
0x28c09355…2b41
0x34b655…2a6f
4 touches
1 conflict
0xc852b267…9d14
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity