pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,564,501
← previous block
next block →
recent activity
Analyzing
Block #102,564,501
12 transactions · 12 stateful · 2026-09-06 20:32:54 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,564,501
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xa96df62f
#3
0xa96df62f
#4
matchOrders
#5
0xab083028
· blocks 1
#6
execPerpOps
#7
execFwdPositionOpsV2
· blocks 1
#8
setData
#9
execFwdPositionOpsV2
#10
0xed82b078
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
7
w0
9
w1
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d670066…59e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xf547aa3c…06e6
0x34b655…2a6f
4 touches
1 conflict
0xf635cede…952d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
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
1 conflict on slot
0x0d6700667c…3759e8
Audit this contract →
← previous block
·
next block →
recent activity