pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,549,305
← previous block
next block →
recent activity
Analyzing
Block #95,549,305
8 transactions · 6 stateful · 2026-08-13 05:36:20 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,549,305
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute_route
#2
execOrders
#3
execFwdPositionOps
· blocks 2
#6
setData
#7
0x59558d29
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x2fb55b69…276d
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x3acf9416…7ddc
0x34b655…2a6f
2 touches
0 conflicts
0x3c8d99a5…b937
0x34b655…2a6f
2 touches
0 conflicts
0x3fb49990…ccad
0x34b655…2a6f
2 touches
0 conflicts
0x6939e474…4256
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
3 conflicts on slot
0x0a0cecef55…324ed0
Audit this contract →
← previous block
·
next block →
recent activity