pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,095,070
← previous block
next block →
recent activity
Analyzing
Block #101,095,070
10 transactions · 9 stateful · 2026-09-01 16:54:54 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,095,070
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x8263f5d9
#2
execOrders
#3
execOrder
· blocks 3
#6
0x6a9703d6
#7
executeBatch
#8
setData
#4
execOrder
· blocks 2
#5
0x0c7abd22
· 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
5
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e168c8b…6945
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x3602eb96…2683
0x34b655…2a6f
2 touches
0 conflicts
0x46d5925f…afff
0x34b655…2a6f
2 touches
0 conflicts
0x6b267bdf…b173
0x34b655…2a6f
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
6 conflicts on slot
0x1e168c8bca…f56945
Audit this contract →
← previous block
·
next block →
recent activity