pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,736,816
← previous block
next block →
recent activity
Analyzing
Block #95,736,816
6 transactions · 6 stateful · 2026-08-13 21:20:31 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,736,816
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#3
0x6a7e3597
#4
setData
#5
execOrders
#2
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7318f4f…a42f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x03a99334…6aed
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x228aeacb…9bd9
0x34b655…2a6f
2 touches
0 conflicts
0x25e65ccc…c735
0x34b655…2a6f
2 touches
0 conflicts
0x3750b746…5a9e
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
0xc7318f4f0f…a8a42f
Audit this contract →
← previous block
·
next block →
recent activity