pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,474,612
← previous block
next block →
recent activity
Analyzing
Block #95,474,612
10 transactions · 8 stateful · 2026-08-12 23:20:39 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,474,612
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#7
0x6a7d003e
#8
setData
#9
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9cd8eb0…09af
0x34b655…2a6f
4 touches
1 conflict
0x138c3b86…eff8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc9cd8eb0…09ae
0x34b655…2a6f
4 touches
1 conflict
0x396fec1d…8746
0x34b655…2a6f
2 touches
0 conflicts
0x3e2cd42c…600e
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6571
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
0xc9cd8eb023…a209af
Audit this contract →
← previous block
·
next block →
recent activity