pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,572,132
← previous block
next block →
recent activity
Analyzing
Block #102,572,132
12 transactions · 11 stateful · 2026-09-06 21:11:37 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,572,132
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
0xab083028
#4
0xab083028
#5
0x59558d29
#6
execPerpOps
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
execFwdPositionOpsV2
#11
transfer
#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
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e5c8276…2941
0x34b655…2a6f
4 touches
1 conflict
0x73bb65fc…650d
0x754704…b603
2 touches
0 conflicts
0xc98b6062…73eb
0x754704…b603
2 touches
0 conflicts
0xd1eae902…bfd4
0x754704…b603
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
0x0110331c13…54b891
Audit this contract →
← previous block
·
next block →
recent activity