pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,383,007
← previous block
next block →
recent activity
Analyzing
Block #98,383,007
12 transactions · 11 stateful · 2026-08-23 04:25:56 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
#98,383,007
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
execPerpOps
#4
execPerpOps
#5
0x5acec890
#6
0x928e4afa
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
0x57368ddf
#11
execOrders
#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
0xc9c17729…ac91
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1cfa777f…cb6c
0x34b655…2a6f
2 touches
0 conflicts
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5399cb08…fd77
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
0xc9c17729ae…44ac91
Audit this contract →
← previous block
·
next block →
recent activity