pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,621,628
← previous block
next block →
recent activity
Analyzing
Block #96,621,628
10 transactions · 10 stateful · 2026-08-16 23:31:39 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,621,628
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
0x5acec890
#3
execOrders
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 1
#6
0x3f5c179b
#7
execFwdPositionOpsV2
#9
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x7aa91b8f…d070
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6aa2
0x2b46c0…1669
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
0xc824469a90…af6426
Audit this contract →
← previous block
·
next block →
recent activity