pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,321,603
← previous block
next block →
recent activity
Analyzing
Block #101,321,603
12 transactions · 10 stateful · 2026-09-02 11:54:34 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,321,603
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrder
#3
0xab083028
#4
0xab083028
#5
0x59558d29
#6
0x3f5c179b
#7
0x3f5c179b
#8
execFwdPositionOpsV2
· blocks 1
#10
execOrders
#11
setData
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeddebb1d…4dd4
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xaa1d7fa6…69bb
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xba078c04…9572
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot
0xeddebb1d0b…f54dd4
Audit this contract →
← previous block
·
next block →
recent activity