pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,207,444
← previous block
next block →
recent activity
Analyzing
Block #99,207,444
13 transactions · 11 stateful · 2026-08-26 02:17:01 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,207,444
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5acec890
· blocks 1
#4
forward
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
batchUpdate
#9
execFwdPositionOpsV2
· blocks 1
#10
relay
#11
setData
#3
0x5acec890
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26253352…1a75
0x34b655…2a6f
4 touches
1 conflict
0xf3a3c1e7…3f14
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1fc96968…a760
0x34b655…2a6f
2 touches
0 conflicts
0x4a99ba46…452f
0x34b655…2a6f
2 touches
0 conflicts
0x4d454f64…09ee
0x34b655…2a6f
2 touches
0 conflicts
0x5e90fc97…7b9d
0x34b655…2a6f
2 touches
0 conflicts
0x67acc7c6…6bee
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
0x26253352cc…671a75
Audit this contract →
← previous block
·
next block →
recent activity