pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,299,383
← previous block
next block →
recent activity
Analyzing
Block #101,299,383
13 transactions · 11 stateful · 2026-09-02 10:02:45 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,299,383
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x575c0012
#2
matchOrders
#3
0x5acec890
#4
execOrder
· blocks 1
#6
execOrder
#7
execPerpOps
#8
execPerpOps
#9
setData
#10
execFwdPositionOpsV2
#11
0x6a97f4bd
#12
execOrders
#5
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x04c70b12…1178
0x34b655…2a6f
2 touches
0 conflicts
0x1f3accc0…b9c5
0x34b655…2a6f
2 touches
0 conflicts
0x88e92ec7…696d
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
1 conflict on slot
0x038b92433d…c5553d
Audit this contract →
← previous block
·
next block →
recent activity