pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,488,722
← previous block
next block →
recent activity
Analyzing
Block #99,488,722
11 transactions · 11 stateful · 2026-08-27 01:52:58 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,488,722
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 1
#3
execOrders
#4
execOrder
· blocks 1
#5
0x59558d29
#6
setData
#8
execFwdPositionOpsV2
#9
0x6a8f98f2
#7
execFwdPositionOpsV2
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x059e0ac0…0267
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00500a94…20d5
0x34b655…2a6f
2 touches
0 conflicts
0x2965e2d6…5800
0x34b655…2a6f
2 touches
0 conflicts
0x6f6266c7…b8e3
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
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
0x059e0ac09d…0f0267
Audit this contract →
← previous block
·
next block →
recent activity