pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,014,965
← previous block
next block →
recent activity
Analyzing
Block #102,014,965
13 transactions · 12 stateful · 2026-09-04 22:07:48 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,014,965
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
0xab083028
#4
0xab083028
#5
execPerpOps
#6
execPerpOps
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
batchUpdate
#11
commit
#12
0x6a9b41ac
#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
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xaceaf2ae…52e8
0x34b655…2a6f
4 touches
1 conflict
0xb0a4a49b…0f55
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd6de2989…db19
0x34b655…2a6f
4 touches
1 conflict
0xf6197d2e…5650
0x34b655…2a6f
3 touches
1 conflict
0x0147266d…695a
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
1 conflict on slot
0xfaf89f4544…89ced6
Audit this contract →
← previous block
·
next block →
recent activity