pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,011,813
← previous block
next block →
recent activity
Analyzing
Block #102,011,813
14 transactions · 11 stateful · 2026-09-04 21:51:53 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,011,813
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x5acec890
#4
0x5acec890
· blocks 1
#5
execPerpOps
#6
execPerpOps
#7
setData
#8
execFwdPositionOpsV2
#9
updatePriceFeedsIfNecessary
#10
forward
#12
execOrders
#13
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x673dc967…24bc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0259de4d…a4dd
0x34b655…2a6f
2 touches
0 conflicts
0x313ed009…2f7d
0x34b655…2a6f
2 touches
0 conflicts
0x6215b5b4…149a
0x34b655…2a6f
2 touches
0 conflicts
0x764c3e36…c6db
0x34b655…2a6f
2 touches
0 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
2 touches
0 conflicts
0xab539396…b4bb
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
0x673dc9672e…df24bc
Audit this contract →
← previous block
·
next block →
recent activity