pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,527,545
← previous block
next block →
recent activity
Analyzing
Block #98,527,545
10 transactions · 10 stateful · 2026-08-23 16:39:00 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,527,545
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
0x59558d29
#4
0x5acec890
#5
execFwdPositionOpsV2
· blocks 1
#6
setData
#8
0x6a8b229c
#7
execFwdPositionOpsV2
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x95fd6588…311e
0x34b655…2a6f
4 touches
1 conflict
0xa34c2102…57aa
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
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
0xf51ec09cc1…a1b4a9
Audit this contract →
← previous block
·
next block →
recent activity