pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,554,350
← previous block
next block →
recent activity
Analyzing
Block #95,554,350
12 transactions · 10 stateful · 2026-08-13 06:01:42 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,554,350
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0xe33905c2
#3
execPerpOps
#4
execPerpOps
#5
execFwdPositionOps
· blocks 1
#6
executeBatch
#8
0x6a7d5e3e
#9
setData
#10
0x59558d29
#11
0x61d59c2d
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1a1a29a…a399
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a398
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x4010a00e…baad
0x34b655…2a6f
2 touches
0 conflicts
0x70a474ce…81dd
0x34b655…2a6f
2 touches
0 conflicts
0x7f0431af…c549
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
0xe1a1a29a1a…3aa399
Audit this contract →
← previous block
·
next block →
recent activity